Support for VVV 2.0

[Mte90]

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

[leogopal]

Would be so keen for this for vvv2.0 👍

[bradp]

Super related: #330

[tomjn]

We should create a VVV 2 milestone to track support across multiple issues

[ivankristianto]

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.

[tomjn]

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.

1. Figure out what's wanted
2. Put it in vvv-custom.yml
3. Reprovision

There's no avoiding the reprovision

[matthewfarlymn]

Is VV still being developed for VVV 2.0?

[Mte90]

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.

[tomjn]

VVV itself has a custom site template repo that does mostly the same thing:

• https://github.com/Varying-Vagrant-Vagrants/custom-site-template
• https://github.com/Varying-Vagrant-Vagrants/custom-site-template-develop

[giantleif]

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.

[tomjn]

People using VVV may be interested in watching Varying-Vagrant-Vagrants/VVV#1262