search

WordPress / meta-environment

A collection of scripts that provision the official WordPress.org websites into a Varying Vagrant Vagrants installation.
190 stars 69 forks source link

Move Nginx configs and vvv hosts files #126

Closed tomjn closed 5 years ago

tomjn commented 5 years ago

VVV preferentially checks .vvv/ and provision subfolders in the root to save time. If it doesn't find what it's looking for though, it'll do a costly subfolder search.

At the moment the main example for keeping this subfolder search is this meta environment. In addition, it will always load all the nginx configs and all the hosts files anyway because of how the provisioner works, even if the user only wants wptv provisioning for example.

So why not move them all into a provision subfolder, and merge the files? It's faster, and easier to maintain. I'd have preferred a .vvv folder, but best to be back compatible.

I also removed the hardcoding on the folder name, so now the meta environment will still work if you name the site wpmeta or meta, although it will be a bit strange if you have more than one defined but it was already like that.

Future optimisations would involve a provision/vvv-init.sh that runs the other vvv-init.sh files. Ideally having checked the config first

tomjn commented 5 years ago

It might also be possible to parallelise provisioning the sites once a common vvv-init.sh is present

tomjn commented 5 years ago

This closes #125 and #9

iandunn commented 5 years ago

Thanks Tom!

We might need to update /docs/troubleshooting.md because of the pathname changes, but that's a low priority.