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
.test TLD is now used for all default VVV sites instead of
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
With WP-CLI, it’s pretty straight forward:
wp option update home http://src.wordpress-develop.test
wp option update siteurl http://src.wordpress-develop.test
On new provisions of VVV, this will all be setup automatically. On your own custom sites, you’ll need to adjust accordingly. Embrace the
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.
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.
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!
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!