Open jversmis opened 8 years ago
For now, my workaround is to remove the vvv-init.sh files when the site has been set up.
I'd like to figure this out too. Against the concept of Vagrant, I know, I use one box to host 15+ domains. Backups of stuff online, mostly. Also to save hard drive space, in not having multiple boxes, and to save having to spin up boxes individually. One VM for many. But when I create a new site, the command runs provision on all existing sites under that VM, which slows the whole process greatly. Wondering how to get around this exactly.
I've just run into this too... and thinking that perhaps a flag could be used on create to specify that the site should not be auto updated when a provision
is run?
If this isn't a crazy idea then I'd be happy to put together a PR, looks like the lines around here could be tweaked to offer the behaviour .
Ah right, I see this project has been forked... ignore me. And thanks for great tool :)
When i create a new site from the vagrant root folder with command "vvv-site-wizard/vvv", all the existing sites are being updated to the latest wordpress version.
Is this default behaviour? Is it possible to create a new site without having the other sites updated as well?