With the release of Chrome 63 in December 2017 came extra grumbling from developers. The reason for this turmoil is because Chrome now forces https:// on any site that uses the .dev Top Level Domain (TLD). To help alleviate the pain, here is a step by step guide to change a VVV site from .dev to .local (you can follow the same instructions for any TLD that you wish to use).
- Open up VVV/config/nginx-config/sites/yoursitedomain.conf in your favorite text editor.
- On line 37, update the `server_name` from `yoursitedomain.dev …` to `yoursitedomain.local … `
- Now open VVV/www/yoursitedomain/vvv-hosts and update its contents to `yoursitedomain.local`
- In Finder, open VVV/www/yoursitedomain/htdocs/wp-config.php and update all references to `.dev` to `.local`
- Using your preferred method, update your hosts file so that it now knows to point your IP to yoursitedomain.local instead of yoursitedomain.dev
- In terminal, cd into your VVV root directory.
`vagrant provision`. This may take a few minutes.
- Visit your new site at yoursitedomain.local
You will have to follow this process for each domain that you would like to move from .dev to .local. If you are changing multiple sites, you will only need to run steps 6 and 7 once.
Last updated byon .