VVV

VVV 3.5.1

Fri, 23 Oct 2020 20:00:00 +0000

The new (v3.5.1 it is for us a huge improvements about code organization but also on testing side. The develop branch has now moved to 3.6.0 in preparation for a 3.6.1 release in several months time.

3.5.1

This release introduce a new Vagrant plugin developed by us (but is available to everyone), vagrant-goodhosts. This vagrant plugin started as fork of vagrant-hostsupdater and is a wrapper of GoodHosts CLI that improves support for various OS. To get more information you can check the release post on daniele.tech.

Check out the changelog for more details on what changed in VVV 3.5

Provisioners and Utilities

Our utilities and site templates run on a continuous release process. Here’s a quick update of what changed since VVV 3.5.0.

Custom-site-template

wp-cli.yml now include aliases to be able to access the VM with WP-CLI itself
public_html folder can be customized with a parameter

Check the readme for all the features!

Custom-site-template-develop

Improved .gitignore

Check the readme for all the features!

Utilities

Graphviz is now an utility graphviz
opcache-gui utility added, Opcache-Gui is an alternative to opcache-status that is abandoned
php80 is now available
tideways utility was updated to support the latest XhGUI version
nvm utility added
svn-folder-upgrade utility added for upgrading old SVN repositories

Documentation

Improved docs about provisioners
Added new external utility on doc about WordMove integration

VVV Slack

We have a Slack Workspace! This is a great place to get help/support, ask quick questions, or watch VVV being developed. (Find out more about the VVV Slack.

VVV 3.4.1

Thu, 04 Jun 2020 20:00:00 +0000

We’ve been hard at work and have released (v3.4.1. The develop branch has now moved to 3.5.0 in preparation for a 3.5.1 release in several months time

Before we continue, here’s a recap of what changed in 3.3:

Installs the ntp date packages and starts the ntp service to fix time drift on sleep
Fixes an issue with the ntpsec package by removing it
Fixed the use of dots in site names breaking provisioning
Improvements to the ruby code in the vagrant file

3.4.1

This release contains a number improvements to terminal output, logging, and bugfixes. We also made a lot of small internal improvements to provisioners to improve reliability in edge cases.

Enhancements

Improved the log folder names from 20200225-182126 to 2020.02.25-18-21-26 (#2078 )
Added a switch_php_debugmod to replace the xdebug_on tideways_off style scripts (#2084
Checks the default password for MySQL root user during provision (#2077, (#2085 )
Removed NVM cleanup code (#2088 )
Improved the provider examples in default-config.yml (#2091 )
Run rubocop on Vagrantfile in a move towards more idiomatic ruby (#2093 )
Improved network checks to test more domains (#2099 )
ack-grep is now installed via apt rather than beyondgrep.com (#2100 )
Refactor site provisioners (#2102 )
Added new bears to the various vagrant trigger scripts (#2105, (#2108 )
Removed Ubuntu news MOTD (#2105 )
Improve network checks wording (#2106 )
Support for vagrant-hostmanager (#2112 )
Bumped MariaDB sources from 10.3 to 10.4 (#2140 )
Improve compatibility with globally installed gems on the guest (#2138 )
Add LFTP tool (#2137 )
List relevant log files when provisioners fail (#2161 )

Bug Fixes

Fix checks for utility installation (#2073 )
Fix SSL issue on the base Ubuntu image (#2074 )
Don’t spider and recurse domains when checking for network connections (#2103 )
Always set the database root user password to avoid having the default invalid password on fresh installs (#2104 )
Swap the MariaDB apt mirror used for a more reliable source ( partially #2140 and in a217369 )
Fixed an issue with the dpkg lock file not being cleaned up sometimes (#2151 )
Fix issues with the sad bear showing at the end of provisioning despite provisioners being succesful (#2161
Fix provisioners printing all output to console (not just errors) (#2174 )

Check out the changelog for more details on what changed in VVV 3.4

Provisioners and Utilities

Our utilities and site templates run on a continuous release process. Here’s a quick update of what changed since VVV 3.3.0.

Custom-site-template

New option to set the db table prefix
Expire static assets after 100 days

Check the readme for all the features!

Custom-site-template-develop

New parameter to set if SVN or GIT should be used to download the repo
NPM improvements

Check the readme for all the features!

Utilities

Improved TLS_CA provisioner for issues with certifications
Improvements to Tideways provisioners
php-intl module is now installed

Documentation

Improved docs for Tideways and XHGui
Vagrantfile documentation
Documented how works the NGINX config generation
SSH troubleshooting updated
Log folder documentation
Hosts file troubleshooting

VVV Slack

We have a Slack Workspace! This is a great place to get help/support, ask quick questions, or watch VVV being developed. (Find out more about the VVV Slack.

VVV 3.2.0

Thu, 31 Oct 2019 20:00:00 +0000

Hi! Welcome to the very late release post for VVV v3.2.0.

The biggest change is that we no longer use vvv-custom.yml, we’ve moved to config/config.yml. VVV will auto-migrate the file on the next command ran after update, and the format is still the same. We also changed site provisioning to log output to log files instead of the terminal. Terminal output should be much smaller and friendlier. We’ve also fixed a number of Hyper-V/Parallels/VMWare bugs.

Check out the changelog for more details on what changed in VVV 3.2

VVV Slack

We now have a Slack Workspace! This is a great place to get help/support, ask quick questions, or watch VVV being developed. Find out more about the VVV Slack.

Provisioners and Utilities

Our utilities and site templates run on a continuous release process. Here’s a quick update of what changed since VVV 3.1.0.

Custom-site-template

Support for custom Nginx configs: https://github.com/Varying-Vagrant-Vagrants/custom-site-template/pull/26/
Force installation of specific WordPress versions: https://github.com/Varying-Vagrant-Vagrants/custom-site-template/pull/28
Theme installation support: https://github.com/Varying-Vagrant-Vagrants/custom-site-template/pull/29
Setup sites from SQL dumps: https://github.com/Varying-Vagrant-Vagrants/custom-site-template/pull/25
Set strict script execution for site provisioners: https://github.com/Varying-Vagrant-Vagrants/custom-site-template/pull/27
Support redirecting attachments not found locally to an external domain. https://github.com/Varying-Vagrant-Vagrants/custom-site-template/pull/24
Attempt to install backups of the DB if they’re found while provision: https://github.com/Varying-Vagrant-Vagrants/custom-site-template/pull/23
Allow installing test content: https://github.com/Varying-Vagrant-Vagrants/custom-site-template/pull/21
Allow configurable admin users: https://github.com/Varying-Vagrant-Vagrants/custom-site-template/pull/20
Avoid downloading first in english, and then switching language. https://github.com/Varying-Vagrant-Vagrants/custom-site-template/pull/19
Allow dashes in database names: https://github.com/Varying-Vagrant-Vagrants/custom-site-template/pull/18
Support for custom constants and values: https://github.com/Varying-Vagrant-Vagrants/custom-site-template/pull/16

Check the readme for all the features!

Custom-site-template-develop

Custom Nginx Support and Updates: https://github.com/Varying-Vagrant-Vagrants/custom-site-template-develop/pull/17
Fix #1868: Grunt/Webpack output on template-develop in a file: https://github.com/Varying-Vagrant-Vagrants/custom-site-template-develop/pull/16
Fix 1943: https://github.com/Varying-Vagrant-Vagrants/custom-site-template-develop/pull/15

Check the readme for all the features!

Utilities

Add WPCli-dev utilities: https://github.com/Varying-Vagrant-Vagrants/vvv-utilities/pull/35
Fix vvv_config file path for Tideways: https://github.com/Varying-Vagrant-Vagrants/vvv-utilities/pull/38
Remove define of a global var: https://github.com/Varying-Vagrant-Vagrants/vvv-utilities/pull/37
Simplify PHP installation: https://github.com/Varying-Vagrant-Vagrants/vvv-utilities/pull/36
Adds PHP 7.4 utility https://github.com/Varying-Vagrant-Vagrants/vvv-utilities/pull/34
add a http header when tideways is enabled, and adjust the conditional https://github.com/Varying-Vagrant-Vagrants/vvv-utilities/pull/32
Fix 1924: https://github.com/Varying-Vagrant-Vagrants/vvv-utilities/pull/33

We also added 2 new utilities:

wpcli-dev, which adds a WP CLI developer build for contributing to the WP CLI project.
php, automatically installs all versions of PHP.

Documentation

Document the versioning system used by VVV: https://github.com/Varying-Vagrant-Vagrants/VVV/issues/1050
Profiling with tideways isn’t working as stated in the documentation https://github.com/Varying-Vagrant-Vagrants/VVV/issues/1911
Update documentation to reflect which sites are auto provisioned https://github.com/Varying-Vagrant-Vagrants/VVV/issues/1944
Improved docs for local dev: multisite: https://github.com/Varying-Vagrant-Vagrants/VVV/issues/1941
How to declare plugin options (version, activate, etc.) in vvv-custom.yml: https://github.com/Varying-Vagrant-Vagrants/VVV/issues/1935
Vagrant + Windows = : https://github.com/Varying-Vagrant-Vagrants/VVV/issues/1682
Replace Docs examples with links: https://github.com/Varying-Vagrant-Vagrants/VVV/issues/1676
Other improvements to Tideways utility: https://github.com/Varying-Vagrant-Vagrants/VVV/issues/1761

VVV 3.1.0

Thu, 04 Jul 2019 18:00:00 +0000

Hi! Welcome to the very late release post for VVV v3.1.0.

This is primarily a reliability update. Note that updating to v3.1 requires a vagrant destroy and a vagrant up --provision. Back up your database before updating.

Enhancements

The vagrant box can now be overriden using the box parameter in vvv-custom.yml under the vm_config section. This requires a vagrant destroy followed by a vagrant up --provision to recreate the VM using the new box
The main provisioner now only fetches the apt keys once rather than on every key check
The TTY fix shell provisioner and the /vagrant setup shell provisioner were merged for a minor reduction in provisioning time.
Allow db_backup script to be run manually regardless if automatic DB backups are disabled
vvv, vvv.dev, and vvv.local now redirect to vvv.test
Added a premade Sequel Pro config file under the database folder
Set GitHub token from vvv-custom.yml for Composer

Bug Fixes

Changed to the ubuntu/bionic64 box to avoid issues with kernel page cache corruption until they can be identified, these were causing issues when updating a WP installation
Fixes to mysql user and group creation to improve shared folder reliability
Fixed an issue with permissions in files copied to the home folder
Fixed shared folder and permissions for Microsoft Hyper-V
Fixed all mount_options to the correct permissions for Microsoft Hyper-V
Set VM Name to exactly the same as VirtualBox, using v.vmname for Hyper-V
Fixes to log file paths for XDebug and PHP
Fixes files and folders in the home folder being owned by root instead of vagrant
Fixes support for database names containing hyphens in the import/restore scripts
Fixes the site provisioner attempting to clone site templates into existing sites when a site template is added to a site that didn’t have one before, but has already provisioned ( it will note that this happened but won’t clone the template )
Removed some references to Go
Fixed symlink issues with apt source files by copying instead
Specify keep_colors on vagrant provisioners to prevent composer from outputting valid messages in the red error colours, unnecessarily alarming users
xdebug_on and xdebug_off now toggle Tideways so that XDebug and Tideways are never running at the same time
Switched to Node v10 by default to fix compatibility issues with the WP Core build scripts
Runs the npm commands in the main provisioner under the vagrant user
Node v11 is now auto-downgraded to Node v10
Fixed Database SSH access from the host by enabling password authentication in /etc/ssh/sshd_config
Added code to remove NVM
Change Permission folder /vagrant from root to vagrant

VVV 3.0

Wed, 15 May 2019 18:00:00 +0000

Hi! Welcome to the very late release post for VVV v3.0. As we follow semantic versioning, this is a breaking release, and requires slightly different update instructions.

Ubuntu 14 EOL and moving to Ubuntu 18 LTS

VVV 2 uses Ubuntu 14, but this reached end of life recently. In response Ondrej deleted the unsupported PHP packages, and all VVV 2 installs were no longer able to provision. VVV contributors had setup a package mirror in case this had happened, but it seems only 70% of the needed packages were mirrored.

For this reason, VVV 2 is no longer supported, and won’t be recieving fixes and updates.

VVV 3 moves us to a new Ubuntu 18.04 LTS box, which should cover us until 2024. Additionally, we’re using a leaner custom built box. This does mean that you will need to destroy your VM to update:

# turn off the VM
vagrant halt
# destroy the Ubuntu 14 VM
vagrant destroy
# pull down the latest update
git pull
# provision a shiny new Ubuntu 18 VM
vagrant up --provision

This will destroy the database, but luckily VVV has been creating backups for a long time, you can restore them after updating with this command:

vagrant ssh -c "db_restore"

If you turned off database backups, you can manually back up your database before updating with this command:

vagrant ssh -c "db_backup"

What Else Has Changed?

MariaDB data No Longer Inside the VM

VVV3 stores its database in database/data now, which means it will survive a vagrant destroy. If you’re having trouble provisioning mariadb, let us know on github issues.

We also added a config option to return to the old behaviour for those having problems:

general:
  db_share_type: false

We continued optimising provision in this release, and making VVV friendlier.

Vagrant Guest Additions Plugin Disabled

Our new box has recent guest additions, so this shouldn’t be needed. However, some users like this plugin, and when reprovisioning encountered problems. We’ve disabled the plugin just for VVV to avoid these issues.

Changes To Utilities

Utilities are now simpler and easier to work with and debug:

TLS certificates are now accessed via a new /srv/certificates folder
Utilities are now announced with messages for if no provisioner was found
The trusted hosts utility has been deprecated and merged into the core provisioner, fixing several dashboard cloning issues
VVV2 referred to utilities internally as resources, this has been changed to utilities, and they’re now cloned to the provision/utilities folder

Mapped Folder Changes

With this release, we removed the /vagrant mapped folder and eliminated overlapping vagrant shared folders. This improves compatibility, the new shares are:

/srv/provision -> provision
/srv/certificates -> certificates
/srv/config -> config
/srv/database -> database/sql
/var/lib/mysql -> database/data
/var/logs/nginx -> logs/nginx
/var/logs/php -> logs/php
/var/logs/memcached -> logs/memcached
/srv/www -> www

VVV will now copy the version and vvv-custom.yml file on provision into /vagrant inside the VM, but this folder is no longer mounted and is erased on every provision prior to copying.

Ubuntu 18 Changes

Ubuntu brings with it lots of Kernel improvements that make Ubuntu faster in a virtual machine. Expect to see small to large performance improvements in some areas depending on your machine and workload.

We also had the opportunity to update some packages, Mongodb has been updated from v3.4 to v4.0, and various security improvements have been inherited.

Provisioning Improvements

We also improved the provisioners:

The Git PPA is now only added if it’s missing
Various composer and git commands now run as root ( VirtualBox determines the ownership of those folders, so they will always be owned by the vagrant user )
The branch and repo URL are mentioned when cloning dashboards, sites, and utilities
the VVV splash no longer shows on a halt or suspend
when provisioning on Ubuntu 14 it aborts and gives instructions on updating
added the VVV PPA package mirror
nginx now gets reloaded instead of restarted
VVV now copies over a minimal MySQL config for overrides
Added git-svn support
Provisioners now log their output to logs/provisioners/datetime/provisionername.log in addition to showing in the terminal
nvm was removed from the core provisioner, it made a network request on every provision, and downloaded a script that always failed with syntax errors

VirtualBox and Vagrant Versions

If you’re using the 6.x versions of VirtualBox, be sure to update to v6.0.8 which contains several important fixes regarding shared folders.

We also now require Vagrant v2.2.4 as a minimum version.

.dev Domains Removed

We deprecated these a while ago, but vvv.dev is no longer added as a host or listened for by Nginx. We also removed vvv.local, and vvv.localhost to avoid confusion. From now on vvv.test is the dashboard URL.

As an aside, vvv gets added, and we’d like to remove it, but aren’t sure how. If you know how to do it, let us know!

Finally, a Big Thank You To Our Testers

To make sure we eliminated as many kinks and issues as possible, we had a large pool of testers, community members who took their own time to help verify and find problems. I have no doubt some still remain, and I hope a v3.1 will be out in the next week or two. Dealing with the sudden changes to Ubuntu 14 have been tough on a lot of people, and a major disruption to others, thank you for being patient!

VVV 2.6

Mon, 01 Apr 2019 18:00:00 +0000

Hi! Welcome to the very late release post for VVV v2.6. For help updating, see the documentation on keeping VVV up to date.

We continued optimising provision in this release, and making VVV friendlier.

Splash and Completion Messages

We improved our splash screen to contain better debug info for when users raise GitHub issues. We also noticed that users who finished provisioning weren’t sure if it had finished or stopped. To fix this, we added a big message that appears at the end of provisioning and vagrant up to make it clear the process has finished:

Hosts Updater AutoDownload

If the gem for hostsupdater is in the same folder, but the plugin isn’t installed, it will auto-install it. It will also try to auto-install via Vagrant. VVV requires hostsupdater to function as expected.

2.4 also allowed Utilities to add their own Nginx configs, and renamed the sites that come bundled with VVV by default. 2.4 also fixed some logging issues with PHP. Otherwise v2.4 was a short release that focused on cleaning up messaging.

Contributor Day Changes

A wordcamp_contributor_day_box option was added to the config file to make it easy for contributor day users to switch to mainline VVV.

Tideways and xhgui Profiling

If you add tideways to your utilities section as shown in the default vvv-config.yml then reprovision, you will gain access to xhgui and advanced PHP profiling features. Add ?enable-tideways to a URL and it will show up in xhgui at http://xhgui.vvv.test

VVV 2.4 and 2.5

Sun, 31 Mar 2019 18:00:00 +0000

Hi! Welcome to the very late release post for VVV v2.4 and v2.5. For help updating, see the documentation on keeping VVV up to date.

Here’s what’s happening…

Notable Changes in 2.4

Both versions focused on optimising the provisioning process further, 2.4 continues this by only provisioning hosts for active sites.

Notable Changes in v2.5

2.5 made a number of provisioning improvements and general updates:

DB backups can now be turned on and off in the config file, see vvv-config.yml for details
MailHog is installed via binaries rather than being built from source, saving a lot of time, and removing golang
VVV now preferentially loads provisioner files from .vvv and provision, if they’re found it won’t search the subfolders for provisioner files
VVV warns you if you don’t put any hosts on your site
Site provisioners can now use {vvv_tls_cert} and {vvv_tls_key}, no need for a sed command to add them
More warnings and messages for provisioners to make it clearer what’s going on

A Reminder, Uninstall Vagrant Triggers and upgrade Vagrant to 2.2.4+

At the time of writing the latest Vagrant version is 2.2.4, we strongly recommend updating. The Vagrant triggers plugin is also no longer required, as it was merged into Vagrant 2.1.

Remember:

VirtualBox creates the VM
Vagrant manages the VM, turning it on and off, configuring it
VVV tels vagrant how to configure it, and how to install things

This does mean that users with the triggers plugin installed will get a warning when using vagrant commands. Read the warning for a parameter that can be added to silence the warning if you still need vagrant triggers for pre-2.1 vagrant environments. Otherwise, uninstall vagrant triggers with the following command:

vagrant plugin uninstall vagrant-triggers

We recommend a minimum of Vagrant 2.2.4, and suggest avoiding v2.1.3 which is known to be a broken Vagrant release.

Varying Vagrant Vagrants 2.3.0

Sun, 30 Sep 2018 18:00:00 +0000

Hi! Welcome to the release post for Varying Vagrant Vagrants 2.3.0. For help updating, see the documentation on keeping VVV up to date.

Here’s what’s happening…

MailCatcher Replaced With MailHog

MailCatcher was proving difficult to support, and very fragile. In response, we’ve now replaced it with the superior MailHog. MailHog can be accessed via the dashboard at vvv.test

Git LFS

Support was added for Git LFS type repositories, and has been tested with site templates. No additional steps are needed on the VVV side to support this.

Improved Fallbacks

VVV will no longer continue to provision if packages installation or network detection fails. We’ve also changed our tests to use the Launchpad PPA servers rather than Google, enabling Chinese users to run VVV!

We also:

Improved the built in terminal prompt
Removed the MOTD instruction to manually update packages that broke VVV installs
Bundled the apt-get keys as some users failed to retrieve them for unknown reasons

VVV searches 3 levels down for `vvv_hosts`

Instead of searching 4 levels down, VVV will search 3 folders down. There has also been performance improvements by explicitly searching for provisioner files where VVV expects them, and avoiding the search altogether.

Remember, vvv_hosts support, and being able to put provisioner files anywhere is included for legacy support reasons only. Nested VVV sites can be handled via the vm_dir and local_dir parameters without requiring slow filesystem searches.

Logs

Logs are now owned by the vagant user not the ubuntu user, which should improve support for providers such as hyperV and others

A Reminder, Uninstall Vagrant Triggers and upgrade Vagrant to 2.1.5+

Since v2.2.x VVV now requires Vagrant 2.1 to run. The Vagrant triggers plugin is also no longer required, as it was merged into Vagrant 2.1.

Remember:

VirtualBox creates the VM
Vagrant manages the VM, turning it on and off, configuring it
VVV tels vagrant how to configure it, and how to install things

vagrant plugin uninstall vagrant-triggers

We recommend a minimum of Vagrant 2.1.4, and suggest avoiding v2.1.3 which is known to be a broken Vagrant release.

Varying Vagrant Vagrants 2.2.1

Tue, 22 May 2018 22:00:00 +0000

Hi! Welcome to the release post for Varying Vagrant Vagrants 2.2.1. For help updating, see the documentation on keeping VVV up to date.

Here’s what’s happening…

Vagrant Triggers and Vagrant 2.1

VVV now requires Vagrant 2.1 to run. The Vagrant triggers plugin is also no longer required, as it was merged into Vagrant 2.1.

vagrant plugin uninstall vagrant-triggers

PHP 7.2

VVV now uses PHP 7.2 by default. See here on how to change a sites PHP version.

TLS

Testing with https is an important part of development, so we’ve added a new TLS-CA utility, that comes with new installs by default. This installs a certificate authority just for your machine, letting you test https:// addresses locally.

To use this, add the utility, and reprovision. Then, you need to tell your OS or browser to accept the root certificate for the authority. This tells your computer to trust any certificates it generates, without which you’ll get a warning when visiting sites. This can be found in your VVV folder under certificates/ca/ca.crt.

For more information, see our docs here

Custom Site Template Develop and Deprecations

The wordpress-develop repository has been deprecated! This old site template was hardcoded to a single URL, and had other issues. It’s replaced by custom-site-template-develop, which allows for multiple WP core development environments.

Additionally, the src. subdomain is going away due to changes in the WP core development process.

Logs

Logs are now in the /var/log folder, which is mounted on to the log folder in your install. In particular, the default Nginx log, and the MariaDB logs are now in /var/log

Dashboard

Is now a separate git repo! And updates independently of VVV on vagrant provision. You can also override the dashboard in vvv-custom.yml via the dashboard options:

dashboard:
  repo: ....
  branch; ...

Project Notes

We’ve added a new contributor team for testers and reviewers, Benjamin Lu and Daniele Scasciafratte. They’ve been very helpful in issues and testing changes. We’ve also added Tom J Nowell as a lead developer.

Varying Vagrant Vagrants 2.1.0

Wed, 08 Nov 2017 17:00:00 +0000

Hi! Welcome to the release post for Varying Vagrant Vagrants 2.1.0. For help updating, see the documentation on keeping VVV up to date.

Here’s what’s happening…

A new TLD for default sites

The .test TLD is now used for all default VVV sites instead of .dev.

You may have noticed back in September that Google added their .dev TLD to the HTTPS preload list in Google Chrome. This means that in recent versions of Chrome .dev domains are forced to use HTTPS.

Up until this point, VVV relied heavily on the .dev TLD and moving to a TLD that isn’t owned by anyone is a pretty obvious move. After quite a bit of discussion, we determined that .test was the best of the options laid out in RFC2606.

Because we can’t detect all customizations made to default sites, automatically updating everything isn’t an option. Default sites like src.wordpress-develop.dev will still work at their current URLs and will require a bit of manual effort to move over to src.wordpress-develop.test.

With WP-CLI, it’s pretty straight forward:

vagrant ssh
cd /srv/www/wordpress-develop/public_html
wp search-replace '.dev' '.test' --recurse-objects --network

On new provisions of VVV, this will all be setup automatically. On your own custom sites, you’ll need to adjust accordingly. Embrace the .test domain!

Update: We’ve added more extensive instructions for migrating from .dev to .test here

Thanks to Gary for warning us about this 2.5 years ago. :)

Better and better documentation

Many updates to VVV’s documentation on varyingvagrantvagrants.org were made between the release of 2.0.0 and now.

The process to contributing to documentation has changed to use the varyingvagrantvagrants.org repository. This clears the workflow for shipping documentation changes to proceed separately from shipping VVV releases.

There has also been a great improvement in the quality and presentation of the documentation. Things look great, are navigable, and you can search!

As a bonus, check out all the excellent work that’s been done on the VVV dashboard at your local http://vvv.test site.

And more

A full changelog is up that has all of the details for this release. We fixed MailCatcher, made some tweaks to how PHPCS is installed and its configuration, and applied some small adjustments to the VM configuration.

Project notes

Wayyyyyy back in April, we added Tom J Nowell as a VVV committer and he’s been doing a fantastic job of staying on top of things. He’s been a prolific contributor this year, much of the current state of our documentation structure is due to his work, and he made our excellent logo!

Future thoughts

There’s always a lot to think about for the future of VVV, but I’ll note a couple things that are coming up:

At some point we’ll want to move to the latest Ubuntu LTS release. This will be a breaking change and require a 3.x.x.
We may also take this opportunity to refactor how provisioning is done and instead provide our own base box.
Have more ideas? Come on over and participate!

That’s all for 2.1.0. A big thank you to every one of our contributors and thank you for using VVV!

VVV

VVV 3.5.1

3.5.1

Provisioners and Utilities

Custom-site-template

Custom-site-template-develop

Utilities

Documentation

VVV Slack

VVV 3.4.1

3.4.1

Enhancements

Bug Fixes

Provisioners and Utilities

Custom-site-template

Custom-site-template-develop

Utilities

Documentation

VVV Slack

VVV 3.2.0

VVV Slack

Provisioners and Utilities

Custom-site-template

Custom-site-template-develop

Utilities

Documentation

VVV 3.1.0

Enhancements

Bug Fixes

VVV 3.0

Ubuntu 14 EOL and moving to Ubuntu 18 LTS

What Else Has Changed?

MariaDB data No Longer Inside the VM

Vagrant Guest Additions Plugin Disabled

Changes To Utilities

Mapped Folder Changes

Ubuntu 18 Changes

Provisioning Improvements

VirtualBox and Vagrant Versions

.dev Domains Removed

Finally, a Big Thank You To Our Testers

VVV 2.6

Splash and Completion Messages

Hosts Updater AutoDownload

Contributor Day Changes

Tideways and xhgui Profiling

VVV 2.4 and 2.5

Notable Changes in 2.4

Notable Changes in v2.5

A Reminder, Uninstall Vagrant Triggers and upgrade Vagrant to 2.2.4+

Varying Vagrant Vagrants 2.3.0

MailCatcher Replaced With MailHog

Git LFS

Improved Fallbacks

VVV searches 3 levels down for vvv_hosts

Logs

A Reminder, Uninstall Vagrant Triggers and upgrade Vagrant to 2.1.5+

Varying Vagrant Vagrants 2.2.1

Vagrant Triggers and Vagrant 2.1

PHP 7.2

TLS

Custom Site Template Develop and Deprecations

Logs

Dashboard

Project Notes

Varying Vagrant Vagrants 2.1.0

A new TLD for default sites

Better and better documentation

And more

Project notes

Future thoughts

VVV searches 3 levels down for `vvv_hosts`