-
Notifications
You must be signed in to change notification settings - Fork 847
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to disable installation of default WP sites #313
Comments
I am thinking the same. |
@cfoellmann that would be perfect. Would save tons of time provisioning. The Commenting out a block in the Vagrant file would also work great as @thewebists suggested. |
done in #319 |
Agreed, it would be great to split things up a bit. I'll take a look at @cfoellmann's PR as it's likely in the right direction. See also #210. For the immediate future, you can hack it a bit by creating directories for each installation before provisioning. This will skip the main creation of the sites, though may cause some errors to display during provisioning. Ugly, but something. :) |
any news? |
It is now possible to disable the provisioning of sites after the merge of #980. 🎉 |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
As much as I like the idea of having quick and easy access to the different versions of WP installed by default with VVV, in practice this is only rarely useful for me personally, while making the vagrant provision process take longer.
I would like to propose two things:
The ability to disable the installation of the default WP sites (by commenting out a block in the Vagrantfile).
Split off the WP provisioning scripts into a separate file. This would help with the above, make it easier to customize/hack the provision.sh file and give the option of running the script independently of the provision process to add the WP site manually.
The text was updated successfully, but these errors were encountered: