VVV: what two vagrant commands build, and what the README leaves to the docs site
An open source Vagrant configuration for developing with WordPress
At a glance
- What is it?
- Varying Vagrant Vagrants provisions a Linux server for WordPress work through Vagrant and a provider such as VirtualBox, Docker or Parallels Pro. The quick start is two commands and a config file, while requirements and the package list live on the documentation site.
- Who is it for?
- Use VVV when your WordPress work needs a throwaway Linux server with the stack already assembled, and set aside time to download and provision that VM the first time. Skip it when you cannot run a hypervisor or a container provider, or when your team needs to reproduce an environment from a lockfile the repository does not contain.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 160 days ago.
- What is it written in?
- Mainly Shell, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- Varying-Vagrant-Vagrants/VVV4,526 ★ · +1
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| Varying-Vagrant-Vagrants/VVV | 4.5k | 4.5k |
1 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Two vagrant commands and nothing else in the quick start
The How To Use section is two shell commands, run after you have installed Vagrant and a provider and cloned the repository:
vagrant plugin install --local
vagrant up --provisionThe order matters. The first installs plugins for this project only, the `--local` flag scoping them to the checkout rather than to your user directory, so a fresh clone needs it before anything in the Vagrantfile can resolve. The second builds the machine and runs the provisioning pass in one step, and the README's description of the result is the whole promise: a VM capable of hosting sites. Nothing between those two lines is optional and nothing after them is explained, which makes this the complete documented path from clone to running environment. Everything deeper, including the provider matrix and the exact package set, is deferred to the documentation site.
config/config.yml is the only knob the quick start names
Once the machine is up, the README gives you two things to do and one file to edit. You can visit `http://vvv.test` to see the default sites that came with the environment. Or you add a site, and the way to do that is a YAML file at `config/config.yml`, which the project says will create a new site under the `www` subfolder. That file gets little guidance in the README, since the quick start does not show its shape, its keys or what a minimal entry looks like. The documentation site is where that has to come from.
The default branch is develop while the tags are 3.x
VVV develops on a branch called `develop`, not on `master` or `main`, and the releases are tagged in a plain numeric series: v3.15.1 published 2025-05-21, 3.13.2 on 2024-07-19 and 3.13.1 on 2024-06-16. Two repository files help you tell what state you are in. `CHANGELOG.md` at the root is where the release history lives, and a `version` file sits beside it, which is the cheapest way to check the version of a checkout before you spend an hour provisioning it. The gap between the newest tag and the newest push is worth noting too: the last push on `develop` is dated 2026-06-08, more than a year after v3.15.1. Nothing in the README says whether `develop` is meant for daily use or whether a released tag is the safer starting point, so that choice is yours to make deliberately.
The provider list changes between the intro and the how-to
Two different provider lists appear, and the difference is not reconciled. The opening paragraph says VVV uses Vagrant and Docker, VirtualBox, Parallels or HyperV to create a Linux server environment. The How To Use section tells you to install Vagrant and a provider such as VirtualBox, Docker, or Parallels Pro, which drops HyperV and switches Parallels to the paid Pro edition. So the reader who took the first sentence literally and installed HyperV is not contradicted outright, but is not pointed at it either, and the reader on Parallels finds the paid product named in the instructions. Since the provider decides what you have to install on the host and what your VM looks like once it boots, pick the one your machine supports and confirm it against the installation documentation before running anything.
No teardown, suspend or update command appears anywhere
The README covers exactly one lifecycle event, the initial `vagrant up --provision`. There is no documented command for stopping the machine, suspending it, throwing it away, or updating the base box, and no section on what to do when a provision run fails halfway. That omission has a cost, because the environment is a provisioned VM holding site code, a database directory and logs, and destroying it is the operation people most need spelled out. The tree shows where that state lives, with `database/`, `log/` and `www/` at the root alongside `provision/`, but the documentation does not connect those directories to any command. Until you read the docs site, treat every Vagrant command beyond the two documented ones as something you are choosing on your own responsibility.
provision/, database/, log/ and www/ are the stateful directories
The root listing explains what a VVV checkout is made of, and it divides cleanly into machine definition and machine state. `Vagrantfile` defines the machine, `provision/` holds what runs during `vagrant up --provision`, and `config/` holds the site configuration. Then come the directories that accumulate your work: `database/` for data, `log/` for output, and `www/` for the sites served under `vvv.test`, which is where a new entry in `config/config.yml` ends up. Two more root files are easy to overlook. `wp-cli.yml` configures WP-CLI inside the environment, and `.vscode/` is checked in, which means editor settings travel with the project. `log/` and `database/` being committed or ignored is decided by `.gitignore`, and that decision matters before your first push.
CLAUDE.md and agents.md sit beside the contributing docs
The root of this repository carries both `CLAUDE.md` and `agents.md`, next to `CODE_OF_CONDUCT.md` and `CONTRIBUTING`-style pointers in the README. The README routes contributions to a contributing guidelines page on the documentation site rather than to a file in the repository, so the guidance a contributor is expected to follow lives off the checkout. The two agent instruction files are not mentioned in the README at all. For an outside contributor that means the fastest way to understand the conventions is to read those two files first, then follow the site link for the formal guidelines. It also means the repository advertises two sources of project conventions, and nothing in the README tells you which one wins when they disagree.
System requirements and the package list are both off-repository
The README declines to state any requirement numbers. Minimum system requirements are handled by a link to the software requirements page on the documentation site, and the software actually installed is handled by a link to the installed packages page, phrased as the place for a full list. That is an honest arrangement for a project whose package set changes with the release, and it also means the repository alone cannot answer the two questions that decide whether VVV will run on your machine: how much disk and memory the VM needs, and what ends up inside it. Both answers are one click away, so check them against the release you are actually provisioning.
Editorial conclusion
Use VVV when your WordPress work needs a throwaway Linux server with the stack already assembled, and set aside time to download and provision that VM the first time. Skip it when you cannot run a hypervisor or a container provider, or when your team needs to reproduce an environment from a lockfile the repository does not contain. Before your first `vagrant up --provision`, read the software requirements page and the installed packages page, because the README carries no requirement numbers, and decide where your own site config will live, since `config/config.yml` is the only file the quick start names.
Frequently asked questions
What is Vagrant used for in a VVV setup?
VVV uses Vagrant with a provider such as VirtualBox, Docker, Parallels Pro or HyperV to create a Linux server environment for building sites. Running vagrant up --provision produces a VM capable of hosting sites.
What exactly is Vagrant in the VVV quick start?
You install Vagrant and a provider, clone the repository, then run vagrant plugin install --local followed by vagrant up --provision. After that, http://vvv.test serves the default sites.
Is Vagrant free to use for VVV development?
VVV itself is MIT licensed open source. The licensing question sits with Vagrant and with the provider you choose, such as VirtualBox, Docker, Parallels Pro or HyperV, and the repository does not state the terms for any of them.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/varying-vagrant-vagrants-vvv)Star history chart for your README
[](https://hysenlabs.com/projects/varying-vagrant-vagrants-vvv)Was this useful?