First make sure you have all the necessary software installed for Vagrant to run listed in the software requirements section.
There are 2 methods to getting VVV, but we recommend using
git as it makes updating much easier
This is the recommended method for installing VVV. Clone the main VVV repo into a local directory:
git clone -b master git://github.com/Varying-Vagrant-Vagrants/VVV.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
There are 2 methods, both involve downloading a zip file:
- download and extract the repository
developbranch zip file to a
vagrant-localdirectory on your computer.
- OR download and extract a stable release zip file if you’d like some extra comfort.
Note: We strongly recommend using the
git method, it makes updating VVV to get new features and fixes significantly easier.
Once you’ve installed everything, copy
vvv-custom.yml. Any changes to
vvv-config.yml will get overwritten when you update VVV, so always make changes to
- In a command prompt, change into the new directory with
- Start the Vagrant environment with
- 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
supassword may be required to properly modify the hosts file on your local machine.
- Visit the VVV Dashboard at http://vvv.test to view your new WordPress sites.
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.
- Preferred: If the virtual machine has been powered off with
vagrant upwill quickly power on the machine without provisioning.
- Rare: If you would like to reapply the provisioning scripts with
vagrant up --provisionor
vagrant provision, some time will be taken to check for updates and packages that have not been installed.
- Very Rare: If the virtual machine has been destroyed with
vagrant destroy, it will need to download the full 100MB of package data on the next