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

Auto-site setup all the things #210

Closed
simonwheatley opened this issue Nov 24, 2013 · 7 comments
Closed

Auto-site setup all the things #210

simonwheatley opened this issue Nov 24, 2013 · 7 comments
Labels
Milestone

Comments

@simonwheatley
Copy link
Contributor

@simonwheatley simonwheatley commented Nov 24, 2013

43272801

Should we move all the sites in the www directory to use the auto-site setup method? Dog fooding, and all that. Plus it'd give handy built in examples for people.

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 wordpress-default and wordpress-develop and wordpress-trunk)?

@jeremyfelt
Copy link
Member

@jeremyfelt jeremyfelt commented Nov 25, 2013

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 git clone or something.

@tnorthcutt
Copy link
Contributor

@tnorthcutt tnorthcutt commented Jan 31, 2014

One option might be to make e.g. -default, -develop, and -trunk easy switched on (or off) by commenting out a line in one of the setup scripts. I'm talking over my own head here, but I get the impression that's doable.

@markchitty
Copy link

@markchitty markchitty commented Feb 12, 2014

+1 for easily switching on/off the -default / -develop / -trunk WP sites.

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 wordpress-develop, wordpress-default and wordpress-trunk directories under /www (as suggested here https://groups.google.com/forum/#!topic/wordpress-and-vagrant/NHiXTLHCIA8), but that still leaves the stub databases around in MySQL and the hosts entries from vvv-hosts. Being able to switch them off prior to running vagrant up would also save a bunch of download time when you first set up the VM.

Just started using VVV today so apologies if this is a noob perspective.

@jeremyfelt
Copy link
Member

@jeremyfelt jeremyfelt commented Feb 13, 2014

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

@cfoellmann
Copy link
Member

@cfoellmann cfoellmann commented Apr 3, 2014

See #319 for the implementation of this

@jeremyfelt jeremyfelt modified the milestones: 1.3 Release, 1.2 Release May 5, 2014
@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

The dream has been realized in #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.

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