A few WordPress Core committers are trying out Flywheel for developing WordPress, BuddyPress, bbPress, and so on. I, for one, really like the direction y’all are taking it, so I’m planning on trying to replace VVV with it full-time.
When setting up a new site, we are presented with 2 options: “Preferred” and “Custom”
I think this makes total sense, and would be hard to improve, but one thing that isn’t obvious is it is also the gateway to whether or not
/app/conf/ is created. If you pick “Preferred” you aren’t able to tweak the configuration to later use that site for development. (I understand why this is, and don’t recommend changing it.)
I think it’d be neat to see a third major option here: “Core Contribution” or the like.
This option could do the following 2 things:
git clone git://develop.git.wordpress.org/ .into
This would essentially create a basic, turn-key, WordPress Core Contributor environment. There are certainly other tweaks that could happen, and it could be implemented in several other ways, but the common hang-up so far has been that the “Preferred” option doesn’t create a
/conf/ directory, and since it’s the default option and we are learning how Local works, it’s the first mistake I made (and watched someone else make, too) without an obvious path to get WordPress cloned and Nginx looking at
(We had to delete the site, recreate it using the “Custom” option, stop the server, edit
site.conf, start the server, and then everything was good to go. Not a ton of hard work, but tedious to do for every local site.)
Keep up the great work. Thanks for everything!