Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update documentation to reflect which sites are auto provisioned #1944

Closed
joedolson opened this issue Sep 25, 2019 · 4 comments
Closed

Update documentation to reflect which sites are auto provisioned #1944

joedolson opened this issue Sep 25, 2019 · 4 comments

Comments

@joedolson
Copy link

@joedolson joedolson commented Sep 25, 2019

The documentation at https://varyingvagrantvagrants.org/docs/en-US/references/default-sites/ includes trunk.wordpress.test as an automatically provisioned site. However, it is no longer a default site provisioned, and is only provisioned if vvv-custom.yml is edited.

Please update the documentation to reflect behavior more accurately. I think that having a listing of default sites and a listing of default but disabled sites would be useful, including instructions how to enable the disabled sites.

@Mte90
Copy link
Member

@Mte90 Mte90 commented Oct 9, 2019

As I can see that website is still available as default https://github.com/Varying-Vagrant-Vagrants/VVV/blob/develop/vvv-config.yml#L63

GitHub
An open source Vagrant configuration for developing with WordPress - Varying-Vagrant-Vagrants/VVV

@Mte90 Mte90 closed this Oct 9, 2019
@joedolson
Copy link
Author

@joedolson joedolson commented Oct 9, 2019

Skip provisioning is set to true, so it is not provisioned by default.

@Mte90
Copy link
Member

@Mte90 Mte90 commented Oct 9, 2019

Ok I can fix that statement, I misunderstood the point.

@lock
Copy link

@lock lock bot commented Feb 22, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Feb 22, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants