An open source Vagrant configuration for developing with WordPress
MIT License
Bot releases are hidden (Show)
Full Changelog: https://github.com/Varying-Vagrant-Vagrants/VVV/compare/3.13.1...3.13.2
Published by tomjn 4 months ago
Full Changelog: https://github.com/Varying-Vagrant-Vagrants/VVV/compare/3.12...3.13.1
Published by tomjn about 1 year ago
Full Changelog: https://github.com/Varying-Vagrant-Vagrants/VVV/compare/3.11.2...3.12
Published by tomjn over 1 year ago
Fixes for github known hosts
Published by tomjn over 1 year ago
Published by tomjn almost 2 years ago
Full Changelog: https://github.com/Varying-Vagrant-Vagrants/VVV/compare/3.9.1...3.10.1
Published by Mte90 almost 3 years ago
Published by tomjn about 3 years ago
Published by tomjn about 3 years ago
Published by tomjn over 4 years ago
Published by tomjn over 4 years ago
Published by tomjn almost 5 years ago
Published by tomjn about 5 years ago
Published by tomjn about 5 years ago
Published by tomjn about 5 years ago
Published by tomjn over 5 years ago
Published by tomjn almost 6 years ago
Published by tomjn over 6 years ago
Published by jeremyfelt almost 7 years ago
http://vvv.test
) links now open in new tabs. See #1168.vvv-hosts
files in Vagrantfile
. See #1182.varyingvagrantvagrants.org
's Add New Site in the http://vvv.test
dashboard. See #1220.scripts
directory instead of bin
. See #1202.rvm
(which broke MailCatcher). See #1235.phpcodesniffer-standard
to PHPCS's composer.json
. See #1239.Many updates to VVV's documentation were made between the release of 2.0.0 and now. As of 2.1.0, the process to contributing to documentation has changed to use the varyingvagrantvagrants.org repository. This allows the workflow for shipping documentation changes to proceed separately from shipping VVV releases.
Published by jeremyfelt over 7 years ago
VVV 2.0.0 introduces breaking changes in how files are organized and introduces an entirely new method of configuration.
A full vagrant destroy
and vagrant up
are recommended for best results. Running vagrant destroy
will remove your virtual machine entirely and all data stored on the VM will be lost. Please be sure to backup your databases and any files stored in the VM. Files on your local file system will remain, but will still benefit (as always) from a backup.
It is possible to make the from VVV 1.4.x to 2.0.0 without a vagrant destroy
, but the process will involve restructuring several things. Primarily, default project directories are now expected to contain a public_html/
directory. This requires not only file changes, but new Nginx configurations. If you need help troubleshooting, don't hesitate to open a new issue.
Please see the migration documentation for tips on how to manage this process.
The decision to include breaking changes in a release is not made lightly. The new ability to configure your installation of VVV with a vvv-custom.yml
file will make VVV entirely more flexible and maintainable than it has ever been. Please see the release blog post and documentation for more details.
vvv-custom.yml
file that defines which projects, hosts, and utilities are provisioned. See #980.vvv-custom.yml
to quickly add new sites to VVV.vvv-config.yml
and can be used in (or excluded from) custom configurations.vvv-config.yml
and can be used in (or excluded from) custom configurations.php-memcached
package to default provisioning as an alternative to php-memcache
that works with PHP 7.0. See #1076.colordiff
as the default svn diff
command tool. See #1077.