/admin/docker --> /admin/upgrade

This commit is contained in:
Jeff Atwood 2014-08-15 12:31:36 -07:00
parent bca855d80e
commit 7e5678abd5
4 changed files with 5 additions and 5 deletions

View file

@ -1187,7 +1187,7 @@ en:
- See what's new in the [GitHub changelog](https://github.com/discourse/discourse/commits/master). - See what's new in the [GitHub changelog](https://github.com/discourse/discourse/commits/master).
- Upgrade by visiting [%{base_url}/admin/docker](%{base_url}/admin/docker) and pressing the "Upgrade" button. - Upgrade by visiting [%{base_url}/admin/upgrade](%{base_url}/admin/upgrade) and pressing the "Upgrade" button.
- Visit [meta.discourse.org](http://meta.discourse.org) for news, discussion, and support for Discourse. - Visit [meta.discourse.org](http://meta.discourse.org) for news, discussion, and support for Discourse.
@ -1203,7 +1203,7 @@ en:
- See what's new in the [GitHub changelog](https://github.com/discourse/discourse/commits/master). - See what's new in the [GitHub changelog](https://github.com/discourse/discourse/commits/master).
- Upgrade by visiting [%{base_url}/admin/docker](%{base_url}/admin/docker), and pressing the "Upgrade" button. - Upgrade by visiting [%{base_url}/admin/upgrade](%{base_url}/admin/upgrade), and pressing the "Upgrade" button.
- Visit [meta.discourse.org](http://meta.discourse.org) for news, discussion, and support for Discourse. - Visit [meta.discourse.org](http://meta.discourse.org) for news, discussion, and support for Discourse.

View file

@ -196,7 +196,7 @@ See more advice at: http://blog.discourse.org/2014/08/building-a-discourse-commu
- Hopefully you are running [in our Docker container install](https://github.com/discourse/discourse/blob/master/docs/INSTALL.md); it's the only one we officially support. It guarantees easy updates, and all recommended optimizations from the Discourse team. - Hopefully you are running [in our Docker container install](https://github.com/discourse/discourse/blob/master/docs/INSTALL.md); it's the only one we officially support. It guarantees easy updates, and all recommended optimizations from the Discourse team.
- You should get an email notification when new versions of Discourse are released. To upgrade your instance, visit [/admin/docker](/admin/docker) -- <kbd>upgrade</kbd> button will appear. Press it! - You should get an email notification when new versions of Discourse are released. To upgrade your instance, visit [/admin/upgrade](/admin/upgrade) -- <kbd>upgrade</kbd> button will appear. Press it!
- Some other things you might eventually want to set up: - Some other things you might eventually want to set up:
- [Automatic daily backups](https://meta.discourse.org/t/configure-automatic-backups-for-discourse/14855) - [Automatic daily backups](https://meta.discourse.org/t/configure-automatic-backups-for-discourse/14855)

View file

@ -122,7 +122,7 @@ You should see Staff topics and the [Admin Quick Start Guide](https://github.com
# Post-Install Maintenance # Post-Install Maintenance
To **upgrade Discourse to the latest version**, visit `/admin/docker` and follow the instructions. To **upgrade Discourse to the latest version**, visit `/admin/upgrade` and follow the instructions.
The `launcher` command in the `/var/discourse` folder can be used for various kinds of maintenance: The `launcher` command in the `/var/discourse` folder can be used for various kinds of maintenance:

View file

@ -12,7 +12,7 @@ Only admins can perform backups, so sign in as an account with admin access on y
Both the new and old Discourses **MUST BE ON THE EXACT SAME VERSION** to ensure proper backup/export. So the first thing we'll do is update our existing Discourse instance on Linode to the absolute latest version. Both the new and old Discourses **MUST BE ON THE EXACT SAME VERSION** to ensure proper backup/export. So the first thing we'll do is update our existing Discourse instance on Linode to the absolute latest version.
Visit `/admin/docker` to upgrade. Visit `/admin/upgrade` to upgrade.
(If you are running the [deprecated Ubuntu install][dep_ubuntu] you may need to follow [these update instructions][ubuntu_update].) (If you are running the [deprecated Ubuntu install][dep_ubuntu] you may need to follow [these update instructions][ubuntu_update].)