Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Should we move all the sites in the
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
Should we move all the sites in the www directory to use the auto-site setup method? Dog fooding, and all that.
Should we even consider moving some of those sites out into their own repos, allowing VVV to lose a little bloat
I think these three work as just enough bloat. It provides a great core development environment with the ability to flip between latest stable, core.svn, and develop.svn on the fly.
If we did move them out to their own repos, it would be cool. I would want to continue including them by default through
+1 for easily switching on/off the
My WP dev environment consists of:
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
Just started using VVV today so apologies if this is a noob perspective.
@markchitty Welcome! :)
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.