VVV Cheat Sheet

VVV – Varying Vagrant Vagrants

This is a pre-defined Vagrant environment that helps instruct Vagrant how to build a standard WordPress development environment. It includes the provisioning helper scripts to get the MySQL and PHP installs on the virtual machine that Vagrant will run.

It can be installed by downloading the zip file and unzipping it on your laptop or by using git to clone the main repo:

git clone -b master git://github.com/Varying-Vagrant-Vagrants/VVV.git ~/vagrant-local


Vagrant is an open-source software product for building and maintaining portable virtual software development environments, e.g. for VirtualBox, Hyper-V, Docker, VMware, and AWS which try to simplify software configuration management of virtualizations in order to increase development productivity. Vagrant is written in the Ruby language, but its ecosystem supports development in almost all major languages


A copy of your Vagrant systemwide environment. This is the vagrant scripts to help things “go” as well as a subdirectory where the “source box” lives that vagrant up will clone to create your working machine.


Where the VirtualBox “raw” source machine images live.

Vagrant names the images like ubuntu-

Your Vagrant Working Directory: ~/vagrant-local

The typical working directory name is ~/vagrant-local. This is the folder where you unzipped that VVV-develop/zip file or cloned the VVV git repo into.


A file inside the ~/vagrant-local folder if you are using a standard VVV install.

This is the main ruby script that Vagrant will read to decide how to configure a virtual machine. VVV provides this file to tell Vagrant what your virtual machine should look like as well as where to find the helper setup scripts.

It also has info about how to read the new standard vvv-custom.yml file to create additional WordPress test domains inside a single virtual box.

The www subdirectory

A sub-folder inside your VVV install, www contains the meta data as well as main install files for each test domain Vagrant knows about. Inside it there will be a public_html file which contains the code (WordPress in this case) that runs the site.

Vagrant commands

These command will help you work with Vagrant from the command line.

vagrant box list

This command shows the virtual machine images (boxes) that are known to Vagrant. These are typically used as the “source image” to spin up a new box. Essentially cloned to a duplicate image with a unique name that becomes a new running instance.

Post “cloning” the new “installed” images are what show up in VirtualBox.

vagrant box prune

Useful if you’ve been running VVV or Vagrant for a while and have used the vagrant box update command. It removes older stale versions of the “source” machine images.

vagrant package

Creates a “box” from the current Vagrantfile machine setup. Useful for making your own starting image to clone from.


A virtual machine app. Makes pretend servers replicating the hardware of a physical machine in the virtual world of your laptop. It has network drivers, a hard drive, memory, CPUs. The VirtualBox app is a GUI virtual machine manager. VBoxManage is the command line interface that mirrors the GUI commands.

~/Virtualbox VMs

This folder contains the virtual machine images. It is the meta data about the hardware, the current machine state, and the disk image that makes the box “persistent” between vagrant up and halt commands.


A helper app that comes with VirtualBox. Helps manage the virtual machines when the GUI is not available.

This is the default directory where virtual machine images will live. These are the full memory and disk images as well as meta about the machine “hardware” that are created when Vagrant starts up a new machine instance.

VBoxManage list vms

Show a list of the virtual machines on your laptop

vboxmanage unregistervm –delete <id>

MacOS doesn’t care about case with this command, both VBoxManage and vboxmanage run the same command.

Tell VirtualBox to remove a machine image and delete the supporting files from your laptop.

Useful for obliterating a duplicate machine if you had a failed startup. You may want to try to go to VirtualBox first and halt the machine then do a vagrant up or vagrant up –provision first. If not this command may help you start fresh.

This does the same thing as using VirtualBox GUI and right-clicking a stopped (powered off) box and selecting Remove and choosing “Delete All Files

%d bloggers like this: