But that’s in part because VVV made it easier to automate this yourself using a vvv-custom.yml configuration file. And you don’t even have to know what the hell a .yml file is to do it!

All your VVV-Base are belong to us.

The new .yml config makes it easy to create presets for sites you’ll be developing on Vagrant. And the inclusion of a repo section means plenty of people have already put in the hard work to make nice auto setups we can take advantage of.

I like VVV-Base for it’s option for adding plugins and themes to your setup process. As well as deleting existing themes and plugins, multisite setup, db prefixing, and more. All from the comfort of your text-editor.

Setting up a custom .yml file

If you’ve installed VVV already you should have a vagrant-local folder somewhere on your machine3. Within this directory you’ll see a vvv-config.yml file. Duplicate that file and rename it to vvv-custom.yml.

Take a second to read through the comments in the file before you clean it out and drop in the block of code above. You’ll get a good explanation of how the configuration works there.

Once you have your file saved you’ll need to run a provision on your Vagrant. The fastest way to do this is to run the following in your command line vagrant provision --provision-with site-example-site. Simply replace example-site with any additional site names you add in the future and you’re good to go.

If you ever want to skip a site to keep your Vagrant provisioning running quick you can drop in the skip_provisioningVVV parameter to true. Your site configuration and files will still exist, Vagrant just won’t bother provisioning the site when you run vagrant up. This can greatly reduce the number of sites your vagrant needs to setup when you start. And slow start is the main reason I hadn’t gotten around to getting VVV set up on my new laptop.

Conclusion

That’s it. Get out there and start building awesome automated development environments with Vagrant!