summaryrefslogtreecommitdiffstats
path: root/doc/install/Upgrade-Guide.md
diff options
context:
space:
mode:
authorit33 <iantien@gmail.com>2015-11-03 18:30:24 -0800
committerit33 <iantien@gmail.com>2015-11-03 18:30:24 -0800
commit4849eb61ec03126c1d9db4ab8903b3de13333c78 (patch)
tree48fe920cfb3dd4af22f3540f03b6d60f64e0acdc /doc/install/Upgrade-Guide.md
parent3656ba5344cdaa26a5563323f3fe8cb179fac6dd (diff)
downloadchat-4849eb61ec03126c1d9db4ab8903b3de13333c78.tar.gz
chat-4849eb61ec03126c1d9db4ab8903b3de13333c78.tar.bz2
chat-4849eb61ec03126c1d9db4ab8903b3de13333c78.zip
Added post 1.1 install instructions
Diffstat (limited to 'doc/install/Upgrade-Guide.md')
-rw-r--r--doc/install/Upgrade-Guide.md38
1 files changed, 31 insertions, 7 deletions
diff --git a/doc/install/Upgrade-Guide.md b/doc/install/Upgrade-Guide.md
index fc3a0711f..e42b1ba40 100644
--- a/doc/install/Upgrade-Guide.md
+++ b/doc/install/Upgrade-Guide.md
@@ -1,6 +1,35 @@
# Mattermost Upgrade Guide
-### Upgrading Mattermost in GitLab 8.0 to GitLab 8.1 with omnibus
+### Upgrading Mattermost to Next Major Release
+
+Each release of Mattermost contains logic to upgrade it from the previously major build version. For example, version 1.2 upgrades the database and configuration data schema for a Mattermost version 1.1 server. The following procedure outlines how to upgrade Mattermost to the next major release version.
+
+1. Download the **next major build release** of your server
+ 1. Determine the current version of your Mattermost server
+ 1. Go to any team site, opening the main menu at the top right of the left-hand sidebar and selecting **About Mattermost**
+ 2. Identify the next major build release of your Mattermost server from the list of [stable Mattermost releases](https://github.com/mattermost/platform/releases)
+ 1. For example, if your current version is 1.1.0, you want to select version 1.2.0.
+ 1. In some cases there will be **minor build releases**, such as 1.2.1 and 1.2.2. The minor build number indicates a bug fix or security issue release. Testing on minor build versions is less extensive than on major build versions and it is recommended that you use the minor build only if you need the specific additions included.
+ 3. Review Release Notes
+ 1. Check the release notes for the version of Mattermost you are able to install, and note any setting changes in the **Compatibility** section that apply to your deployment
+ 4. Download the `mattermost.tar.gz` file with the correct version for your upgrade.
+2. Stop the Mattermost Server
+ 1. As best practice, consider posting to the Town Square channel of active teams pre-announcing the scheduled downtime to apply these upgrade procedures.
+2. Backup your data
+ 1. Back up your `config.json` file, which contains your system configuration. This will be used to restore your current settings after the new version is installed
+ 2. Backup your database using your organization's standard procedures for backing up MySQL or PostgreSQL
+ 3. If you're using local file storage, back up the location where files are stored
+4. Decompress `mattermost.tar.gz` and use its contents to replace the current version of Mattermost on disk
+5. Restore the state of your server by copying the backed up version of `config.json` in place of the default `config.json`
+6. Start your server and address any setting changes relevant in the latest version of Mattermost
+ 1. The server will upgrade your database schema to be compatibile with the new release, as well as upgrade your `config.json` file to the latest format, using default values for new settings added
+ 2. Go to the System Console to update any settings that have been added or modified based on the **Compatibility** documentation in the release notes
+
+### Upgrading from Mattermost Beta (Version 0.7)
+
+The following instructions apply to updating installations of Mattermost v0.7-Beta to Mattermost 1.1.
+
+#### Upgrading Mattermost in GitLab 8.0 to GitLab 8.1 with omnibus
Mattermost 0.7.1-beta in GitLab 8.0 was a pre-release of Mattermost and Mattermost v1.1.1 in GitLab 8.1 was [updated significantly](https://github.com/mattermost/platform/blob/master/CHANGELOG.md#configjson-changes-from-v07-to-v10) to get to a stable, forwards-compatible platform for Mattermost.
@@ -13,7 +42,7 @@ The Mattermost team didn't think it made sense for GitLab omnibus to attempt an
Optionally, you can use the new [System Console user interface](https://github.com/mattermost/platform/blob/master/doc/install/Configuration-Settings.md) to make changes to your new `config.json` file.
-### Upgrading Mattermost v0.7.1-beta to v1.1.1
+#### Upgrading Mattermost v0.7.1-beta to v1.1.1
_Note: [Mattermost v1.1.1](https://github.com/mattermost/platform/releases/tag/v1.1.1) is a special release of Mattermost v1.1 that upgrades the database to Mattermost v1.1 from EITHER Mattermost v0.7 or Mattermost v1.0. The following instructions are for upgrading from Mattermost v0.7.1-beta to v1.1.1 and skipping the upgrade to Mattermost v1.0._
@@ -26,8 +55,3 @@ If you've manually changed Mattermost v0.7.1-beta configuration by updating the
3. Update your new [`config.json` file in Mattermost v1.1](https://github.com/mattermost/platform/blob/v1.1.0/config/config.json), based on your preferences and the changelog documentation above.
Optionally, you can use the new [System Console user interface](https://github.com/mattermost/platform/blob/master/doc/install/Configuration-Settings.md) to make changes to your new `config.json` file.
-
-
-
-
-