Support for VVV 2.0
Mte90 opened this issue · comments
As I can see https://github.com/Varying-Vagrant-Vagrants/VVV/releases/tag/2.0.0 there are many changes and probably also vv needs an update.
So maybe it is better to release a new version for vv 1.x branch with all the fixes and next a new one for 2.x
Would be so keen for this for vvv2.0 👍
Super related: #330
We should create a VVV 2 milestone to track support across multiple issues
The only way VVV 2 run the provision-sites.sh which will run the vvv-init.sh for each sites is if it is added to vvv_config['sites'].
Right now the workaround I do is: Add the sites to vvv-custom.yml and then run vv create
That will run the site provision.
Anytime the config file changes, re-provision, vagrant reload --provision. VV create should be doing this, it shouldn't be meddling with the internals of VVV, and nothing it does requires that it do so.
- Figure out what's wanted
- Put it in vvv-custom.yml
- Reprovision
There's no avoiding the reprovision
Is VV still being developed for VVV 2.0?
It seems that the alternative is: https://github.com/JPry/vvv-base
As a settings like blueprint but is missing the support for custom constants for the wp-config.php and the rest seems supported.
VVV itself has a custom site template repo that does mostly the same thing:
I removed my current version of vv (which is a later version than the current git repo) after updating to vvv2 and reinstalled using the git repo to vv version 1.3 - all seems to be working now.
This is after completely removing virtualbox and vagrant as well - reinstalling everything fresh.
People using VVV may be interested in watching Varying-Vagrant-Vagrants/VVV#1262