One option might be to make e.g. -default, -develop, and -trunk easy switched on (or off) by commenting out a line in one of the setup scripts. I'm talking over my own head here, but I get the impression that's doable.
The Skeleton framework incorporates Wordpress core as a submodule which lends itself nicely to using git as my deployment engine for the live site, as described here: http://toroid.org/ams/git-website-howto
The WP submodule inside WordPress-Skeleton means I don't want the default VVV WP installs. For now I've switched them off by hand by emptying the wordpress-develop, wordpress-default and wordpress-trunk directories under /www (as suggested here https://groups.google.com/forum/#!topic/wordpress-and-vagrant/NHiXTLHCIA8), but that still leaves the stub databases around in MySQL and the hosts entries from vvv-hosts. Being able to switch them off prior to running vagrant up would also save a bunch of download time when you first set up the VM.
Just started using VVV today so apologies if this is a noob perspective.
I think if we get the auto site stuff setup right, we'll be able to make it possible to disable things with small modifications as @tnorthcutt mentioned. At some point we had a flags system that was more trouble than it was worth, so we'll definitely want to try to avoid that.
Should we move all the sites in the
wwwdirectory to use the auto-site setup method? Dog fooding, and all that. Plus it'd give handy built in examples for people.
Should we even consider moving some of those sites out into their own repos, allowing VVV to lose a little bloat (so we don't have
The text was updated successfully, but these errors were encountered: