From 633a801553ed8fc6ebb87a313d1c2b2522c4e387 Mon Sep 17 00:00:00 2001 From: Daniele Scasciafratte Date: Fri, 17 May 2019 15:02:54 +0200 Subject: [PATCH 1/3] fix #999 --- docs/en-US/references/update-site.md | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 docs/en-US/references/update-site.md diff --git a/docs/en-US/references/update-site.md b/docs/en-US/references/update-site.md new file mode 100644 index 0000000..01daedd --- /dev/null +++ b/docs/en-US/references/update-site.md @@ -0,0 +1,28 @@ +--- +category: 6. Reference +order: 2 +title: Update WordPress websites +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. \ No newline at end of file From 51f8acac09c0dd05ddd9ba81e0f5bb4e92a2df6a Mon Sep 17 00:00:00 2001 From: Tom J Nowell Date: Fri, 17 May 2019 14:13:38 +0100 Subject: [PATCH 2/3] Update update-site.md --- docs/en-US/references/update-site.md | 32 +++++++++++++++------------- 1 file changed, 17 insertions(+), 15 deletions(-) diff --git a/docs/en-US/references/update-site.md b/docs/en-US/references/update-site.md index 01daedd..3087205 100644 --- a/docs/en-US/references/update-site.md +++ b/docs/en-US/references/update-site.md @@ -1,28 +1,30 @@ --- category: 6. Reference order: 2 -title: Update WordPress websites -permalink: /docs/en-US/references/update-wp-sites/ +title: Updating WordPress +permalink: /docs/en-US/references/updating-wp/ --- -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. +VVV will automatically update WordPress on a reprovision if you're using the custom site templates, but this isn't the only or the fastest way to do it ### 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). +As well as reprovisioning, all the normal methods for updating work too, e.g.: + + - Downloading WordPress from WordPress.org and extracting the zip file into `public_html` + - Using the built in updater in the Admin area + - Using WP CLI's core updater command ### 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. +#### Using SVN + +Navigate to the `public_html` folder of the site in a terminal/command prompt, and run `svn up` + +#### Using Git + +Navigate to the `public_html` folder of the site, and run `git pull`. This will happen automatically on reprovision, but only if you're using the default `master` branch -## Manual installation +## Manual WP Installs -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. \ No newline at end of file +Manual installs won't be updated on provision unless a `vvv-init.sh` script has been written to do this. These installs will need to be updated manually, either via WP Admin, WP CLI, or by downloading WordPress From 1cc3baab91b3a627fe02182bf0b152cbab0c5309 Mon Sep 17 00:00:00 2001 From: Tom J Nowell Date: Fri, 17 May 2019 14:14:12 +0100 Subject: [PATCH 3/3] Update update-site.md --- docs/en-US/references/update-site.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/en-US/references/update-site.md b/docs/en-US/references/update-site.md index 3087205..237f91f 100644 --- a/docs/en-US/references/update-site.md +++ b/docs/en-US/references/update-site.md @@ -5,7 +5,7 @@ title: Updating WordPress permalink: /docs/en-US/references/updating-wp/ --- -VVV will automatically update WordPress on a reprovision if you're using the custom site templates, but this isn't the only or the fastest way to do it +VVV will automatically update WordPress on a reprovision if you're using the custom site templates, but there are other methods of updating. ### custom-site-template @@ -19,12 +19,12 @@ As well as reprovisioning, all the normal methods for updating work too, e.g.: #### Using SVN -Navigate to the `public_html` folder of the site in a terminal/command prompt, and run `svn up` +Navigate to the `public_html` folder of the site in a terminal/command prompt, and run `svn up`. #### Using Git -Navigate to the `public_html` folder of the site, and run `git pull`. This will happen automatically on reprovision, but only if you're using the default `master` branch +Navigate to the `public_html` folder of the site, and run `git pull`. This will happen automatically on reprovision, but only if you're using the default `master` branch. ## Manual WP Installs -Manual installs won't be updated on provision unless a `vvv-init.sh` script has been written to do this. These installs will need to be updated manually, either via WP Admin, WP CLI, or by downloading WordPress +Manual installs won't be updated on provision unless a `vvv-init.sh` script has been written to do this. These installs will need to be updated manually, either via WP Admin, WP CLI, or by downloading WordPress.