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

#999: Documentation for updating WordPress #127

Merged
merged 4 commits into from May 17, 2019

Conversation

Projects
None yet
2 participants
@Mte90
Copy link
Contributor

commented May 17, 2019

As usual we can improve it later or during the review: Varying-Vagrant-Vagrants/VVV#999

@Mte90 Mte90 requested a review from tomjn May 17, 2019

@Mte90 Mte90 self-assigned this May 17, 2019

Mte90 and others added some commits May 17, 2019

@tomjn

tomjn approved these changes May 17, 2019

Show resolved Hide resolved docs/en-US/references/update-site.md Outdated
@tomjn

This comment has been minimized.

Copy link
Member

commented May 17, 2019


### custom-site-template-develop

This provisioner use SVN or Git to download the latest trunk updated to the latest commit.
Natively this provisioner downloads the trunk version with SVN but is possible to convert it as Git version with the `develop_git` script.

This comment has been minimized.

Copy link
@Mte90

Mte90 May 17, 2019

Author Contributor

I think that a mention about develop_git can be helpful.

@Mte90

This comment has been minimized.

Copy link
Contributor Author

commented May 17, 2019

I was thinking to add a section:

### Execute only 1 provisioner at once

    vagrant provision --provision-with wordpress-one

This command will execute only the provisioner for the website specified, in this case `wordpress-one`.  
This solution sometimes is preffered instead of executing a provisioning for all the webistes available because is more fast.
@tomjn

This comment has been minimized.

Copy link
Member

commented May 17, 2019

Until we have a provision-site.sh option for utilities, I don't want us encouraging --provision-with, otherwise new sites will provision without a TLS certificate being generated

@tomjn tomjn merged commit 93100e6 into Varying-Vagrant-Vagrants:master May 17, 2019

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.