Varying Vagrant Vagrants logo Varying Vagrant Vagrants

First make sure you have all the necessary software installed for Vagrant to run listed in the software requirements section.

Installing VVV

There are 2 methods to getting VVV, but we recommend using git as it makes updating much easier

With git

This is the recommended method for installing VVV. Clone the main VVV repo into a local directory:

git clone -b master git:// ~/vagrant-local

Alternatively, for faster updates and bleeding edge features, or if you want to help test the next version, use the develop branch instead of the master branch.

Without git

There are 2 methods, both involve downloading a zip file:

Note: We strongly recommend using the git method, it makes updating VVV to get new features and fixes significantly easier.

Post installation

Once you’ve installed everything, copy vvv-config.yml to vvv-custom.yml. Any changes to vvv-config.yml will get overwritten when you update VVV, so always make changes to vvv-custom.yml.

Starting VVV

  1. In a command prompt, change into the new directory with cd vagrant-local.
  2. Start the Vagrant environment with vagrant up.
    • Be patient as the magic happens. This could take a while on the first run as your local machine downloads the required files.
    • Watch as the script ends, as an administrator or su password may be required to properly modify the hosts file on your local machine.
  3. Visit the VVV Dashboard at http://vvv.test to view your new WordPress sites.

Fancy, yeah?

What Did That Do?

The first time you run vagrant up, a packaged box containing a basic virtual machine is downloaded to your local machine and cached for future use. The file used by Varying Vagrant Vagrants contains an installation of Ubuntu 14.04 and is about ~332MB.

After this box is downloaded, it begins to boot as a sandboxed virtual machine using VirtualBox. Once booted, it runs the provisioning script included with VVV. This initiates the download and installation of around 100MB of packages on the new virtual machine.

The time for all of this to happen depends a lot on the speed of your Internet connection. If you are on a fast cable connection, it will likely only take several minutes.

On future runs of vagrant up, the packaged box will be cached on your local machine and Vagrant will only need to apply the requested provisioning.