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.

Sign up for GitHub

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

Jump to bottom

#999: Documentation for updating WordPress #127

Merged
merged 4 commits into from May 17, 2019
Merged

#999: Documentation for updating WordPress #127

Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
633a801
fix #999
Mte90 May 17, 2019
e518b76
Merge branch 'master' into 999
Mte90 May 17, 2019
51f8aca
Update update-site.md
tomjn May 17, 2019
1cc3baa
Update update-site.md
tomjn May 17, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
28 changes: 28 additions & 0 deletions docs/en-US/references/update-site.md
View file
Open in desktop
@@ -0,0 +1,28 @@
---
category: 6. Reference
order: 2
title: Update WordPress websites
tomjn marked this conversation as resolved.
Show resolved Hide resolved
permalink: /docs/en-US/references/update-wp-sites/
---

There are different ways to update a WordPress installation and this depends on what kind of template is used.

## custom-site-template/develop

This provisioners automatically updates the WordPress instance installed when `vagrant provision` is running.
Anyway this provisioners are installing WordPress in different ways.

### custom-site-template

This provisioner use WP-CLI to download and install so is like a native installation but only automated (as example for multisite).

### 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.
In case it is converted this provisioner will use Git to update it.
In both of the cases automatically will execute NPM and Grunt to update the various dependencies.

## Manual installation

WordPress installed with a manual installation can be update using the web interface or using WP-CLI without any problems. Compared to the official provisioners this doesn't include a custom path for the log files or SSL certificates and this need to be done manually.