Consider not updating anything unless box is destroyed #40
Assignees
Milestone
Comments
ghost
assigned
jeremyfelt
added a commit
that referenced
this issue
Apr 8, 2013
Creates a /home/vagrant/initial_provision_run file to track once provisioning has been run on a box for the first time. If this file exists, all apt and composer packages are skipped. Only file linking and WordPress management remains. If the box is ever destroyed, this flag will be deleted and provisioning will run on the next boot. See #40
jeremyfelt
added a commit
that referenced
this issue
Apr 8, 2013
Now that all package installation is wrapped in an initial run flag, the check for apt-get update having been run can be removed. See #40
|
Is this issue resolved with |
|
Yeah, not sure how it didn't get closed. Closing now. :) |
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Through the use of the
/tmp/apt_update_runflag on the guest, we avoid runningapt-get updateon every up, reload or provision. It is only run on the initial up and after a destroy.We should consider doing this for all packages, as this will lower the start up time even more and avoid sudden (albeit unlikely) changes to the dev environment during a normal work day.
It may even be worth wrapping almost the entire provisioning file in a check so only some local project stuff is modified.
Going to play with it throughout the week, may add it to the develop branch early so we can see how it feels.
The text was updated successfully, but these errors were encountered: