You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 30, 2020. It is now read-only.
After adding this in my vvv-custom.yml, 'vv list' shows only the 4 default sites and doesn't show any other sites created with the following way. I've provisioned and the site works fine.
@krismorf This new version of VVV provisions differently and is separate from how VV creates sites. If you ssh into the VM and have a look at the /etc/nginx/sites-available or /etc/nginx/sites-enabled you'll see how these entries are created by the new provisioner that reads that .yml file. The VV way was a more straight forward way of adding these entries.
Until VV is updated, you can do what I do which is to first run vv create and make your site then add your site to the .yml file and run vagrant provision --provision-with site-yoursitename.
This will essentially register the site with VV and make it accessible with the new provisioner. You might run into and issue with the /htdocs folder missing so you might need to create this manually or edit the nginx.conf to not look there for the site-root.
After adding this in my vvv-custom.yml, 'vv list' shows only the 4 default sites and doesn't show any other sites created with the following way. I've provisioned and the site works fine.
The text was updated successfully, but these errors were encountered: