Skip to content
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

Closed
thewebists opened this issue Mar 30, 2014 · 7 comments
Closed

Ability to disable installation of default WP sites #313

thewebists opened this issue Mar 30, 2014 · 7 comments
Labels
Milestone

Comments

@thewebists
Copy link
Contributor

@thewebists thewebists commented Mar 30, 2014

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:

  1. The ability to disable the installation of the default WP sites (by commenting out a block in the Vagrantfile).

  2. 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.

@cfoellmann
Copy link
Member

@cfoellmann cfoellmann commented Apr 1, 2014

I am thinking the same.
It would be far easier to if the 4 included installations were installed via scripts in subfolders under www like www/sites/local.wordpress.dev.
This way users can just drop these and provision without them.

@aronwp
Copy link

@aronwp aronwp commented Apr 2, 2014

@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.

@cfoellmann
Copy link
Member

@cfoellmann cfoellmann commented Apr 3, 2014

done in #319

@jeremyfelt
Copy link
Member

@jeremyfelt jeremyfelt commented Apr 4, 2014

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. :)

@jeremyfelt jeremyfelt added this to the 1.3 Release milestone May 24, 2014
@Mte90
Copy link
Member

@Mte90 Mte90 commented Mar 11, 2015

any news?

@jeremyfelt jeremyfelt modified the milestones: Next Release, Future Release Jul 20, 2015
@jeremyfelt jeremyfelt modified the milestone: Future Release Aug 16, 2016
@jeremyfelt jeremyfelt added this to the 1.5.0 milestone Nov 4, 2016
@jeremyfelt
Copy link
Member

@jeremyfelt jeremyfelt commented Nov 4, 2016

It is now possible to disable the provisioning of sites after the merge of #980. 🎉

@jeremyfelt jeremyfelt closed this Nov 4, 2016
@lock
Copy link

@lock lock bot commented Feb 22, 2020

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.

@lock lock bot locked and limited conversation to collaborators Feb 22, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

5 participants
You can’t perform that action at this time.