Consolide folders into .vvv and move www up 1 level

[tomjn]

For a future release I think it would be good to move the provision and config folders into a .vvv subfolder, then move the default sites location up to the root folder, with some backwards compat code to check for www/ sites that already exist.

Thus a VVV install might look like this:

• .vvv/
• wordpress-default/
• vvv-custom.yml
• Vagrantfile
• LICENSE readme etc..

[Mte90]

uhm maybe can be difficult to do a gitignore with gitpull because there are changes not saved?
I mean I move all the website folders in the root like that and on a git pull what will happen?

[tomjn]

hmmm is there no way around that so that only .vvv and a selection of root folder files are tracked?

[LoreleiAurora]

You can do this like so

# Ignore Everything.
/*
/*/

# Un-ignore the .vvv dir and config file.
!/.vvv/
!/vvv-custom.yml

# Re-ignore the ignored.txt file in the vvv dir.
/.vvv/ignored.txt

[tomjn]

We can probably move things into the .vvv folder and then circle back and see what to do next.

It might also be worth allowing vvv-custom.yml to specify the default folder sites go in, and use www as the default value, then change that to "" to test

[tomjn]

For the moment I've decided that moving www up one level can be done in the future once some things are figured out, since /srv/www gets mapped on to it, and that would go away if changed. Speaking with @LoreleiAurora though we need to map individual site folders rather than the entire folder

[tomjn]

closing this for now, we might revisit this in the future

[lock]

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.