-
Notifications
You must be signed in to change notification settings - Fork 5
upgrades
Minor updates to the ce-vm stack are normally backward compatible, and performed automatically on each vagrant up/halt. You can turn off the automatic pulling by setting the "ce_vm_upstream_auto_pull" variable to "false".
Any updates that break backward compatibilty (change in Vagrantfile, structure, ...) is considered a "major" release and is not automatically applied.
It is normally possible to keep using different major version in parallel (eg. 3.x for some projects, 4.x for others), so existing projects should still continue to work without porting them to a new version. After a while though, version requirements for Vagrant/Docker will necessarily diverge.
Due to mount point persistence, for each "major" upgrade, after following the steps below, you will need to vagrant destroy your project and vagrant up again.
Version 7.x is only "major" in that it fixes an issue with the auto update mechanism. It is fully backward compatible with version 6.x.
Replace the project Vagrantfile with the one from https://github.com/codeenigma/ce-vm-model/blob/7.x/ce-vm/Vagrantfile.
Version 6.x saw some major refactoring internally, but keeps a similar structure externally and "should" be largely backward compatible.
Replace the project Vagrantfile with the one from https://github.com/codeenigma/ce-vm-model/blob/6.x/ce-vm/Vagrantfile.
Version 5.x introduce per service configuration files and new variables.
For simple projects, replacing the project Vagrantfile with the one from https://github.com/codeenigma/ce-vm-model/blob/5.x/ce-vm/Vagrantfile would work, with possibly some "undefined" variables that need to be ported.
Version 4.x drops support for VirtualBox, and remove the use of the vagrant-triggers plugin (as it is not longer maintained). If you want your existing project to continue working, stick with Vagrant 1.9.1.
Replace the project Vagrantfile with the one from https://github.com/codeenigma/ce-vm-model/blob/4.x/ce-vm/Vagrantfile.
Version 3.x brings changes in the structure of projects, and introduces a split between the boilerplate/template project and the core stack.
The structure for the local « custom » folder changes too (for those who have some). In practice it means anything under '/.CodeEnigma/ce-vm/ce-vm-custom/ce-vm' should be moved on level up at '/.CodeEnigma/ce-vm/ce-vm-custom'
Replace the project Vagrantfile with the one from https://github.com/codeenigma/ce-vm-model/blob/3.x/ce-vm/Vagrantfile.
There is no upgrade path from 1.x to 2.x and projects need to be individually ported.