A site in a non-standard folder can still be used via the
local_dir tells VVV where the site is located on the host machine, and
vm_dir tells VVV where the site is located inside the Virtual machine.
Note that when we say site, we mean the entire site folder, complete with
For example, if we put our test sites in a subfolder, we can specify each site like this in the
In the above example, the
local_dir point to the same folder (
vm_dir needs to be an absolute path), however, this doesn’t have to be the case.
In this example, VVV is told to use a site stored outside of the main VVV folder, and mapped to an absolute path in the virtual machine:
Remember that VVV will be expecting an entire site in that folder, not just a WordPress folder or a
wp-content folder. For this reason the above examples use the custom site template.
Custom Subfolder Mappings
You may want to map just the
wp-content folder, or a theme folder. This is not supported by VVV, but it is possible.
To do this, you need to use a vagrant custom file in your site template. However, we do not provide support for users who do this, and it’s assumed that if you do this that you are knowledgable with Vagrant. Having said that, adding synced folders isn’t too difficult, and is documented in great detail on the official Vagrant docs.
Also keep in mind that adding mappings has a performance cost. Users of VVV 1 may remember this process, and to this day some users believe this was officially supported in VVV 1, but this has never been the case.