Vagrant up without additional Wordpress installs and a question about version control

[Matt Messinger]

I mainly build Wordpress themes and plugins, so I have little need for 'wordpress-develop', 'wordpress-trunk', and 'wordpress-cli.' Is there a way to use VVV without including these three extra directories?

Also, If I'm using version control do I really need all these extra files/folders in my project root (like config, database, provision, etc) to muddy up my repo? I thought the only thing a developer needed to create an identical vagrant environment was the Vagrantfile?

Liking Vagrant so far, but would love to iron out the two issues above.

Thanks,

Matt

[Jeremy Felt]

Hey Matt,

The best way to avoid those other directories is to create them as empty beforehand. If the provisioning script checks and see that `wordpress-develop` exists already, it will attempt to run `svn up` and fail rather than checking out the entire project again.

The folder structure for config/database/provision is there mostly for organization. Some of those files are required once the virtual machine is booted to help configure nginx, php, etc so that the development environment does match something resembling production.

- Jeremy

[Matt Messinger]

Jeremy,

Thanks for the quick reply. That makes sense and I'll give your suggestions a try. 

In regards to version control... What's your strategy for committing to git? In particular, do you add certain directories to gitignore? If so, which ones? 

Matt

[Jeremy Felt]

A bunch of stuff is in the default VVV .gitignore that helps the `www/` directory become a place where things can be added at will. You should be able to add a repository to that area without much trouble. In fact, the auto site stuff being worked on at https://github.com/10up/varying-vagrant-vagrants/pull/100 is built around pulling in this modular products that describe themselves to the VVV environment as a whole.

[Henry Scullion]

Matt,

I just got set up with VVV and have the exact same question as you, especially as at the moment MySQL is not consistently being set up on 'vagrant up' and therefore I am doing a lot of 'vagrant up --provision' commands to force it to work, thereby pulling down a lot of WordPress Trunk/Develop/Build updates which I don't need...

Following on from Jeremey's suggestion, did you try the above solution out and did it work? ie delete all the contents (including hidden files) of 'wordpress-develop', 'wordpress-trunk' etc, leaving empty 'wordpress-develop', 'wordpress-trunk' etc directories?

I'm using VVV it as a WordPress site development environment on my Macbook. I add Mark Jaquith's WordPress Skeleton https://github.com/markjaquith/WordPress-Skeleton to the `www/` directory to start off with.

Thanks,
Henry

[Orange Mantra Australia]

Hey Matt Messinger

If you need help for wordpress then our team of experienced wordpress developers can help you. We are available 24 hours to help you.

Conatct us :

Orange Mantra

Web : http://orangemantra.com.au

Email : vi...@orangemantra.com.au