varying-vagrant-vagrants/vvv

An open source Vagrant configuration for developing with WordPress

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 46 minutes ago
Added to GitGenius on September 15th, 2026
Created on December 12th, 2012
Open Issues & Pull Requests: 99 (+0)
GitHub issues: Enabled
Number of forks: 823
Total Stargazers: 4,525 (+0)
Total Subscribers: 130 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.7 hours
Mean response time: 313.6 days
90th percentile: 1931.5 days
Tracked items: 62

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Only 29% of open issues come from outside the core team — the tracker reads mainly as internal planning. Three people close 94% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 24
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,857 days
Stale 30+ days: 24
Stale 90+ days: 23

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • type:feature (32)
  • type:bug (17)
  • type:support (14)
  • type:question (13)
  • type:enhancement (8)
  • priority:low (7)
  • help-wanted (6)
  • provider:virtualbox (6)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

VVV is a Vagrant configuration that creates a local development environment for WordPress developers.

The tool solves the problem of setting up a consistent Linux server environment for WordPress site development and core contribution. It works by using Vagrant with a choice of providers—VirtualBox, Docker, Parallels, or Hyper-V—to spin up a virtual machine. Developers clone the repository, run a setup command, and gain access to a pre-configured server. New sites can be added by editing a configuration file, which automatically creates the corresponding directories and sets up hosting.

WordPress developers building sites or contributing to WordPress itself are the primary audience. The tool is suited for anyone who wants a standardized, reproducible local environment without manually configuring a server. The setup process is straightforward: install Vagrant and a virtualization provider, clone the repository, and run the initialization. The environment includes a default site accessible at a local domain and supports adding multiple sites through configuration.

The project maintains active engagement with its community through documented contribution guidelines and a dedicated website with installation and package documentation. Development activity shows consistent responsiveness to user needs and ongoing refinement of the setup process to support multiple virtualization providers.