You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Drupal VM maintainer now maintains a Drupal VM-optimized pre-provisioned Vagrant base box (Ref: geerlingguy/drupal-vm#1774). This base box dramatically improves the initial build time in situations where the box is already downloaded, and even when the box has not yet been downloaded.
It is similar to the beet/box base box, but uses only the Drupal VM defaults, and will be the default base box for Drupal VM itself. People can still customize and switch to one of the minimal base boxes if they want (after all, the Drupal VM base box is built on Ubuntu 16.04 and not everyone wants that)—or build their own base box (instructions forthcoming... it might be good for BLT to maintain a 100% optimized base box for BLT installs so provisioning would only take a minute or two—but that's a separate issue).
Anyways, in my testing with a basic BLT project I'm maintaining currently, switching to:
vagrant_box: geerlingguy/drupal-vm
sped up cold provisions (where box was not downloaded) by 30%, and warm provisions (where box is already present on the machine) by 60%. And these numbers would likely be even better for people who have less reliable internet connections (e.g. many of those outside the US/North America).
This is a feature request.
The Drupal VM maintainer now maintains a Drupal VM-optimized pre-provisioned Vagrant base box (Ref: geerlingguy/drupal-vm#1774). This base box dramatically improves the initial build time in situations where the box is already downloaded, and even when the box has not yet been downloaded.
It is similar to the
beet/box
base box, but uses only the Drupal VM defaults, and will be the default base box for Drupal VM itself. People can still customize and switch to one of the minimal base boxes if they want (after all, the Drupal VM base box is built on Ubuntu 16.04 and not everyone wants that)—or build their own base box (instructions forthcoming... it might be good for BLT to maintain a 100% optimized base box for BLT installs so provisioning would only take a minute or two—but that's a separate issue).Anyways, in my testing with a basic BLT project I'm maintaining currently, switching to:
sped up cold provisions (where box was not downloaded) by 30%, and warm provisions (where box is already present on the machine) by 60%. And these numbers would likely be even better for people who have less reliable internet connections (e.g. many of those outside the US/North America).
cc @thom8 (currently maintaining
beet/box
)The text was updated successfully, but these errors were encountered: