-
Notifications
You must be signed in to change notification settings - Fork 394
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Speed up VM builds with beetbox #1986
Comments
@geerlingguy Any opinions on using this? |
Beetbox has been well-maintained and I have no problems using it—the only thing I'd want to make sure of is that projects upgrading / switching to it from the other base boxes don't run into any strange side effects. |
I've found it to be far more stable when doing frequent builds as it doesn't depend on a whole bunch of 3rd party services being available (& working) during the VM builds. Also if we're able to get linked clones working again -- geerlingguy/drupal-vm#1528 (I'm using a patch atm) each project only requires a very small amount of disk as it clones from the prebuilt base image. |
As a bonus, it's also smaller than the default base box
|
…in Vm." git commit -m Fixes
…in Vm." git commit -m Fixes
beetbox now offers feature parity with BLT so the preprovisioned base box can be used with Drupal VM.
I've been using it successfully for the last couple of months without any issues and the build times have gone from ~25 mins to ~3 mins.
A new base box is automatically built by Atlas every 2 weeks & build scripts are available in the project if you'd prefer to build your own.
To make use the project base box just create the file --
box/local.config.yml
with the following:workspace
is optional but it's the beetbox default so won't redownload packages that are already available.installed_extras
is only required if you're installing anything in addition to the defaults as everything else is preprovisioned.The text was updated successfully, but these errors were encountered: