From 7523c6f2e6b52c6aaa40900d4b9a6d8b461ba446 Mon Sep 17 00:00:00 2001 From: esethna Date: Wed, 14 Oct 2015 14:36:19 -0600 Subject: Update SMTP instructions Needs dev review. --- doc/install/SMTP-Email-Setup.md | 41 +++++++++++++++++++++++------------------ 1 file changed, 23 insertions(+), 18 deletions(-) (limited to 'doc') diff --git a/doc/install/SMTP-Email-Setup.md b/doc/install/SMTP-Email-Setup.md index 86e2bb20e..0c3004c5f 100644 --- a/doc/install/SMTP-Email-Setup.md +++ b/doc/install/SMTP-Email-Setup.md @@ -1,17 +1,17 @@ ## SMTP Email Setup -In some product evaluation setups email is intentionally bypassed using a `ByPassEmail=true` option. This option allows account creation and system operation without having to set up an email service (e.g. no email verification is required for account creation). This also means neither email notifications nor password reset by email are available. +In some product evaluation setups, email is intentionally bypassed by setting `SendEmailNotifications=false`. This option allows account creation and system operation without having to set up an email service (e.g. no email verification is required for account creation). This also means neither email notifications nor password reset by email are available. -To enable email, turn this option off by setting `ByPassEmail=false` and configuring an SMTP email service as follows: +To enable email, turn this option on by setting `SendEmailNotifications=true` and configuring an SMTP email service as follows: 1. **Set up an SMTP email sending service.** (If you already have credentials for a SMTP server you can skip this step.) 1. [Setup Amazon Simple Email Service](https://console.aws.amazon.com/ses) 2. From the `SMTP Settings` menu click `Create My SMTP Credentials` 3. Copy the `Server Name`, `Port`, `SMTP Username`, and `SMTP Password` 4. From the `Domains` menu setup and verify a new domain. It it also a good practice to enable `Generate DKIM Settings` for this domain. - 5. Choose an email address like `feedback@example.com` for Mattermost to send emails from. - 6. Test sending an email from `feedback@example.com` by clicking the `Send a Test Email` button and verify everything appears to be working correctly. + 5. Choose an email address like `mattermost@example.com` for Mattermost to send emails from. + 6. Test sending an email from `mattermost@example.com` by clicking the `Send a Test Email` button and verify everything appears to be working correctly. 2. **Modify the Mattermost configuration file config.json or config_docker.json with the SMTP information.** 1. If you're running Mattermost on Amazon Beanstalk you can shell into the instance with the following commands 2. `ssh ec2-user@[domain for the docker instance]` @@ -19,20 +19,25 @@ To enable email, turn this option off by setting `ByPassEmail=false` and configu 4. Retrieve the name of the container with `sudo docker ps` 5. `sudo docker exec -ti container_name /bin/bash` 3. **Edit the config file `vi /config_docker.json` with the settings you captured from the step above.** - 1. See an example below and notice `ByPassEmail` has been set to `false` - ``` bash - "EmailSettings": { - "ByPassEmail" : false, - "SMTPUsername": "AKIADTOVBGERKLCBV", - "SMTPPassword": "jcuS8PuvcpGhpgHhlcpT1Mx42pnqMxQY", - "SMTPServer": "email-smtp.us-east-1.amazonaws.com:465", - "UseTLS": true, - "FeedbackEmail": "feedback@example.com", - "FeedbackName": "Feedback", - "ApplePushServer": "", - "ApplePushCertPublic": "", - "ApplePushCertPrivate": "" - } + 1. See an example below and notice `SendEmailNotifications` has been set to `true` + ``` + "EmailSettings": { + "EnableSignUpWithEmail": true, + "SendEmailNotifications": true, + "RequireEmailVerification": true, + "FeedbackName": "No-Reply", + "FeedbackEmail": "mattermost@example.com", + "SMTPUsername": "AFIADTOVDKDLGERR", + "SMTPPassword": "DFKJoiweklsjdflkjOIGHLSDFJewiskdjf", + "SMTPServer": "email-smtp.us-east-1.amazonaws.com", + "SMTPPort": "465", + "ConnectionSecurity": "tls", + "InviteSalt": "bjlSR4QqkXFBr7TP4oDzlfZmcNuH9YoS", + "PasswordResetSalt": "vZ4DcKyVVRlKHHJpexcuXzojkE5PZ5eL", + "ApplePushServer": "", + "ApplePushCertPublic": "", + "ApplePushCertPrivate": "" + }, ``` 4. **Restart Mattermost** 1. Find the process id with `ps -A` and look for the process named `platform` -- cgit v1.2.3-1-g7c22 From ffda0839b6998b861bf6e3fa7ff5bb0b4538b90a Mon Sep 17 00:00:00 2001 From: it33 Date: Wed, 14 Oct 2015 15:26:35 -0700 Subject: Update Slack-Import.md --- doc/help/Slack-Import.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/help/Slack-Import.md b/doc/help/Slack-Import.md index a2914570b..864ed0464 100644 --- a/doc/help/Slack-Import.md +++ b/doc/help/Slack-Import.md @@ -18,5 +18,5 @@ Mattermost currently supports the processing of an "Export" file from Slack cont - Newly added markdown suppport in Slack's Posts 2.0 feature announced on September 28, 2015 is not yet supported. - Slack does not export files or images your team has stored in Slack's database. Mattermost will provide links to the location of your assets in Slack's web UI. - Slack does not export any content from private groups or direct messages that your team has stored in Slack's database. -- The Beta release of Slack Import does not offer pre-checks or roll-back and will not import Slack accounts with username or email address collisions with existing Mattermost accounts. Also, Slack channel names with underscores will not import. Also, mentions do not yet resolve as Mattermost usernames (still shows Slack ID). +- In Beta, Slack accounts with username or email address collisions with existing Mattermost accounts will not import and mentions do not resolve as Mattermost usernames (still shows Slack ID). No pre-check or roll-back is currently offered. -- cgit v1.2.3-1-g7c22 From 57585d6d4fa61de5d9f225f7e827e3021a791558 Mon Sep 17 00:00:00 2001 From: it33 Date: Wed, 14 Oct 2015 15:35:14 -0700 Subject: Update Slack-Import.md --- doc/help/Slack-Import.md | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) (limited to 'doc') diff --git a/doc/help/Slack-Import.md b/doc/help/Slack-Import.md index 864ed0464..e790ca319 100644 --- a/doc/help/Slack-Import.md +++ b/doc/help/Slack-Import.md @@ -1,19 +1,21 @@ -### Slack Import (Beta) +### Slack Import *Note: As a SaaS service, Slack is able to change its export format quickly. If you encounter issues not mentioned in the documentation below, please let us know by [filing an issue](https://github.com/mattermost/platform/issues).* #### Usage -The Slack Import feature in Mattermost is in "Beta" and focus is on supporting migration of teams of less than 100 registered users. The feature can be accessed from by Team Administrators and Team Owners via the `Team Settings -> Import` menu option. +The Slack Import feature in Mattermost is in "Beta" and focus is on supporting migration of teams of less than 100 registered users. To use: -- **It is highly recommended that you test Slack import before applying it to an instance intended for production.** If you use Docker, you can spin up a test instance in one line (`docker run --name mattermost-dev -d --publish 8065:80 mattermost/platform`). If you don't use Docker, there are [step-by-step instructions to install Mattermost in preview mode in less than 5 minutes](../install/Docker-Single-Container.md). +1. Generate a Slack "Export" file from **Slack > Team Settings > Import/Export Data > Export > Start Export** +2. In Mattermost go to **Team Settings > Import > Import from Slack**. Note: Team Owner or Team Administrator role required for this. +3. Click **Select file** to upload Slack export file and click **Import**. +4. Emails and usernames from Slack are used to create new Mattermost accounts +5. Slack users can activate their new Mattermost accounts by using Mattermost's Password Reset screen with their email addresses from Slack to set new passwords for their Mattermost accounts +6. Once logged in, the Mattermost users will have access to previous Slack messages in the public channels imported from Slack. -Mattermost currently supports the processing of an "Export" file from Slack containing account information and public channel archives from a Slack team. +- **It is highly recommended that you test Slack import before applying it to an instance intended for production.** If you use Docker, you can spin up a test instance in one line (`docker run --name mattermost-dev -d --publish 8065:80 mattermost/platform`). If you don't use Docker, there are [step-by-step instructions](../install/Docker-Single-Container.md) to install Mattermost in preview mode in less than 5 minutes. -- Emails and usernames from Slack are used to create new Mattermost accounts, connected to messages history in imported Slack channels. Users can activate these accounts and by going to the Password Reset screen in Mattermost to set new credentials. -- Once logged in, users will have access to previous Slack messages shared in public channels, now imported to Mattermost. - -#### Limitations: +#### Notes: - Newly added markdown suppport in Slack's Posts 2.0 feature announced on September 28, 2015 is not yet supported. - Slack does not export files or images your team has stored in Slack's database. Mattermost will provide links to the location of your assets in Slack's web UI. -- cgit v1.2.3-1-g7c22 From 489eab8609d9b5e7e7ad5801d4c654eed9c91efe Mon Sep 17 00:00:00 2001 From: it33 Date: Wed, 14 Oct 2015 15:36:13 -0700 Subject: Update Slack-Import.md --- doc/help/Slack-Import.md | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) (limited to 'doc') diff --git a/doc/help/Slack-Import.md b/doc/help/Slack-Import.md index e790ca319..906fdbcb1 100644 --- a/doc/help/Slack-Import.md +++ b/doc/help/Slack-Import.md @@ -6,12 +6,17 @@ The Slack Import feature in Mattermost is in "Beta" and focus is on supporting migration of teams of less than 100 registered users. To use: -1. Generate a Slack "Export" file from **Slack > Team Settings > Import/Export Data > Export > Start Export** -2. In Mattermost go to **Team Settings > Import > Import from Slack**. Note: Team Owner or Team Administrator role required for this. -3. Click **Select file** to upload Slack export file and click **Import**. -4. Emails and usernames from Slack are used to create new Mattermost accounts -5. Slack users can activate their new Mattermost accounts by using Mattermost's Password Reset screen with their email addresses from Slack to set new passwords for their Mattermost accounts -6. Once logged in, the Mattermost users will have access to previous Slack messages in the public channels imported from Slack. +1. Generate a Slack "Export" file from **Slack > Team Settings > Import/Export Data > Export > Start Export** + +2. In Mattermost go to **Team Settings > Import > Import from Slack**. Note: Team Owner or Team Administrator role required for this. + +3. Click **Select file** to upload Slack export file and click **Import**. + +4. Emails and usernames from Slack are used to create new Mattermost accounts + +5. Slack users can activate their new Mattermost accounts by using Mattermost's Password Reset screen with their email addresses from Slack to set new passwords for their Mattermost accounts + +6. Once logged in, the Mattermost users will have access to previous Slack messages in the public channels imported from Slack. - **It is highly recommended that you test Slack import before applying it to an instance intended for production.** If you use Docker, you can spin up a test instance in one line (`docker run --name mattermost-dev -d --publish 8065:80 mattermost/platform`). If you don't use Docker, there are [step-by-step instructions](../install/Docker-Single-Container.md) to install Mattermost in preview mode in less than 5 minutes. -- cgit v1.2.3-1-g7c22 From 87d424ab998bdafb6789c50ecd066ae485bff68b Mon Sep 17 00:00:00 2001 From: it33 Date: Wed, 14 Oct 2015 15:36:45 -0700 Subject: Adjusting formatting --- doc/help/Slack-Import.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/help/Slack-Import.md b/doc/help/Slack-Import.md index 906fdbcb1..02f4afc67 100644 --- a/doc/help/Slack-Import.md +++ b/doc/help/Slack-Import.md @@ -18,7 +18,7 @@ The Slack Import feature in Mattermost is in "Beta" and focus is on supporting m 6. Once logged in, the Mattermost users will have access to previous Slack messages in the public channels imported from Slack. -- **It is highly recommended that you test Slack import before applying it to an instance intended for production.** If you use Docker, you can spin up a test instance in one line (`docker run --name mattermost-dev -d --publish 8065:80 mattermost/platform`). If you don't use Docker, there are [step-by-step instructions](../install/Docker-Single-Container.md) to install Mattermost in preview mode in less than 5 minutes. +**It is highly recommended that you test Slack import before applying it to an instance intended for production.** If you use Docker, you can spin up a test instance in one line (`docker run --name mattermost-dev -d --publish 8065:80 mattermost/platform`). If you don't use Docker, there are [step-by-step instructions](../install/Docker-Single-Container.md) to install Mattermost in preview mode in less than 5 minutes. #### Notes: -- cgit v1.2.3-1-g7c22 From 9cd35c46debaa5343239f4c646ec0570c1324cd6 Mon Sep 17 00:00:00 2001 From: it33 Date: Wed, 14 Oct 2015 15:41:24 -0700 Subject: Clarifying instruction --- doc/help/Slack-Import.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/help/Slack-Import.md b/doc/help/Slack-Import.md index 02f4afc67..c54667519 100644 --- a/doc/help/Slack-Import.md +++ b/doc/help/Slack-Import.md @@ -8,7 +8,7 @@ The Slack Import feature in Mattermost is in "Beta" and focus is on supporting m 1. Generate a Slack "Export" file from **Slack > Team Settings > Import/Export Data > Export > Start Export** -2. In Mattermost go to **Team Settings > Import > Import from Slack**. Note: Team Owner or Team Administrator role required for this. +2. In Mattermost go to **Team Settings > Import > Import from Slack**. _Team Owner_ or _Team Administrator_ role is required to access this menu option. 3. Click **Select file** to upload Slack export file and click **Import**. -- cgit v1.2.3-1-g7c22 From 70ddf3f73ee96ab2bcca341fecccd9f3cd250907 Mon Sep 17 00:00:00 2001 From: it33 Date: Wed, 14 Oct 2015 15:42:49 -0700 Subject: Update Slack-Import.md --- doc/help/Slack-Import.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/help/Slack-Import.md b/doc/help/Slack-Import.md index c54667519..1dd250879 100644 --- a/doc/help/Slack-Import.md +++ b/doc/help/Slack-Import.md @@ -1,6 +1,6 @@ ### Slack Import -*Note: As a SaaS service, Slack is able to change its export format quickly. If you encounter issues not mentioned in the documentation below, please let us know by [filing an issue](https://github.com/mattermost/platform/issues).* +*Note: As a proprietary SaaS service, Slack is able to change its export format quickly and without notice. If you encounter issues not mentioned in the documentation below, please let us know by [filing an issue](https://github.com/mattermost/platform/issues).* #### Usage -- cgit v1.2.3-1-g7c22 From 741eb8170f8435c929569c7453af1af5d02520c8 Mon Sep 17 00:00:00 2001 From: it33 Date: Wed, 14 Oct 2015 15:45:05 -0700 Subject: Clarifying description --- doc/help/Slack-Import.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/help/Slack-Import.md b/doc/help/Slack-Import.md index 1dd250879..f834d5177 100644 --- a/doc/help/Slack-Import.md +++ b/doc/help/Slack-Import.md @@ -1,6 +1,6 @@ ### Slack Import -*Note: As a proprietary SaaS service, Slack is able to change its export format quickly and without notice. If you encounter issues not mentioned in the documentation below, please let us know by [filing an issue](https://github.com/mattermost/platform/issues).* +*Note: As a proprietary SaaS service, Slack is able to change its export format quickly and without notice. If you encounter issues not mentioned in the documentation below, please alert the product team by [filing an issue](https://github.com/mattermost/platform/issues).* #### Usage -- cgit v1.2.3-1-g7c22 From e0d2ee3ccee80af95e1191f630802ff3fc1d55e5 Mon Sep 17 00:00:00 2001 From: =Corey Hulen Date: Wed, 14 Oct 2015 19:54:58 -0700 Subject: Fixing doc --- doc/install/SMTP-Email-Setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/install/SMTP-Email-Setup.md b/doc/install/SMTP-Email-Setup.md index 0c3004c5f..b908d04dd 100644 --- a/doc/install/SMTP-Email-Setup.md +++ b/doc/install/SMTP-Email-Setup.md @@ -31,7 +31,7 @@ To enable email, turn this option on by setting `SendEmailNotifications=true` an "SMTPPassword": "DFKJoiweklsjdflkjOIGHLSDFJewiskdjf", "SMTPServer": "email-smtp.us-east-1.amazonaws.com", "SMTPPort": "465", - "ConnectionSecurity": "tls", + "ConnectionSecurity": "TLS", "InviteSalt": "bjlSR4QqkXFBr7TP4oDzlfZmcNuH9YoS", "PasswordResetSalt": "vZ4DcKyVVRlKHHJpexcuXzojkE5PZ5eL", "ApplePushServer": "", -- cgit v1.2.3-1-g7c22 From 9d93f61a2be927c3ff43f270c343c1618bdcd443 Mon Sep 17 00:00:00 2001 From: it33 Date: Wed, 14 Oct 2015 22:01:32 -0700 Subject: Updated to use System Console --- doc/install/SMTP-Email-Setup.md | 81 ++++++++++++++++++----------------------- 1 file changed, 36 insertions(+), 45 deletions(-) (limited to 'doc') diff --git a/doc/install/SMTP-Email-Setup.md b/doc/install/SMTP-Email-Setup.md index 8bf094714..4e06d2f99 100644 --- a/doc/install/SMTP-Email-Setup.md +++ b/doc/install/SMTP-Email-Setup.md @@ -1,55 +1,46 @@ ## SMTP Email Setup -In some product evaluation setups, email is intentionally bypassed by setting `SendEmailNotifications=false`. This option allows account creation and system operation without having to set up an email service (e.g. no email verification is required for account creation). This also means neither email notifications nor password reset by email are available. - -To enable email, turn this option on by setting `SendEmailNotifications=true` and configuring an SMTP email service as follows: - -1. **Set up an SMTP email sending service.** (If you already have credentials for a SMTP server you can skip this step.) - 1. [Setup Amazon Simple Email Service](https://console.aws.amazon.com/ses) - 2. From the `SMTP Settings` menu click `Create My SMTP Credentials` - 3. Copy the `Server Name`, `Port`, `SMTP Username`, and `SMTP Password` - 4. From the `Domains` menu setup and verify a new domain. It it also a good practice to enable `Generate DKIM Settings` for this domain. - 5. Choose an email address like `mattermost@example.com` for Mattermost to send emails from. - 6. Test sending an email from `mattermost@example.com` by clicking the `Send a Test Email` button and verify everything appears to be working correctly. -2. **Modify the Mattermost configuration file config.json or config_docker.json with the SMTP information.** - 1. If you're running Mattermost on Amazon Beanstalk you can shell into the instance with the following commands - 2. `ssh ec2-user@[domain for the docker instance]` - 3. `sudo gpasswd -a ec2-user docker` - 4. Retrieve the name of the container with `sudo docker ps` - 5. `sudo docker exec -ti container_name /bin/bash` -3. **Edit the config file `vi /config_docker.json` with the settings you captured from the step above.** - 1. See an example below and notice `SendEmailNotifications` has been set to `true` - ``` - "EmailSettings": { - "EnableSignUpWithEmail": true, - "SendEmailNotifications": true, - "RequireEmailVerification": true, - "FeedbackName": "No-Reply", - "FeedbackEmail": "mattermost@example.com", - "SMTPUsername": "AFIADTOVDKDLGERR", - "SMTPPassword": "DFKJoiweklsjdflkjOIGHLSDFJewiskdjf", - "SMTPServer": "email-smtp.us-east-1.amazonaws.com", - "SMTPPort": "465", - "ConnectionSecurity": "TLS", - "InviteSalt": "bjlSR4QqkXFBr7TP4oDzlfZmcNuH9YoS", - "PasswordResetSalt": "vZ4DcKyVVRlKHHJpexcuXzojkE5PZ5eL", - "ApplePushServer": "", - "ApplePushCertPublic": "", - "ApplePushCertPrivate": "" - }, - ``` -4. **Restart Mattermost** - 1. Find the process id with `ps -A` and look for the process named `platform` - 2. Kill the process `kill pid` - 3. The service should restart automatically. Verify the Mattermost service is running with `ps -A` - 4. Current logged in users will not be affected, but upon logging out or session expiration users will be required to verify their email address. +In product evaluation setups with single-container Docker instances, email is intentionally disabled. This allows account creation and system operation without having to set up email, but it also means email notification and password reset functionality aren't available. + +### How to enable email + +To enable email, configure an SMTP email service as follows: + +1. **Set up an SMTP email sending service** (if you don't yet have an SMTP service with credentials) + 1. Any SMTP email service can be used, you just need the following information: `Server Name`, `Port`, `SMTP Username`, and `SMTP Password`. + 2. If you don't have an SMTP service, here are simple instructions to set one up with [Amazon Simple Email Service (SES)](https://aws.amazon.com/ses/): + 2. Go to [Amazon SES console](https://console.aws.amazon.com/ses) then `SMTP Settings > Create My SMTP Credentials` + 3. Copy the `Server Name`, `Port`, `SMTP Username`, and `SMTP Password` for Step 2 below. + 4. From the `Domains` menu set up and verify a new domain, then enable `Generate DKIM Settings` for the domain. + 5. Choose an sender address like `mattermost@example.com` and click `Send a Test Email` to verify setup is working correctly. +2. **Configure SMTP settings** + 1. Open the **System Console** by logging into an existing team and accessing "System Console" from the main menu. + 1. Alternatively, if a team doesn't yet exist, go to `http://dockerhost:8065/` in your browser, create a team, then from the main menu click **System Console** + 2. Go to the **Email Settings** tab and configure the following: + 1. **Allow Sign Up With Email:** `true` + 2. **Send Email Notifications:** `true` + 3. **Require Email Verification:** `true` + 4. **Notification Display Name:** Display name on email account sending notifications + 5. **Notification Email Address:** Email address displayed on email account used to send notifications + 6. **SMTP Username**: `SMTP Username` from Step 1 + 7. **SMTP Password**: `SMTP Password` from Step 1 + 8. **SMTP Server**: `SMTP Server` from Step 1 + 9. **SMTP Port**: `SMTP Port` from Step 1 + 10. **Connection Security**: `TLS (Recommended)` + 11. Then click **Save** + +3. **Restart Mattermost** + 1. Use `ps -A` to find the process ID ("pid") for service named `platform` and stop it using `kill [pid]` + 2. The service should restart automatically. Run `ps -A` to verify the `platform` is running again + 3. Use the reset password page (E.g. _example.com/teamname/reset_password_) to test that email is now working by entering your email and clicking **Reset my password**. + 4. Note: The next time users log out, or when their session tokens expire, each will be required to verify their email address. ### Troubleshooting SMTP -If you have issues with your SMTP install, from your Mattermost team site go to the main menu and open `System Console > Logs` to look for error messages related to your setup. You can do a search for the error code to narrow down the issue. Sometimes ISPs require nuanced setups for SMTP and error codes can hint at how to make the proper adjustments. +If you have issues with your SMTP install, from your Mattermost team site go to the main menu and open **System Console -> Logs** to look for error messages related to your setup. You can do a search for the error code to narrow down the issue. Sometimes ISPs require nuanced setups for SMTP and error codes can hint at how to make the proper adjustments. -For example, if `System Console > Logs` has an error code reading: +For example, if **System Console -> Logs** has an error code reading: ``` Connection unsuccessful: Failed to add to email address - 554 5.7.1 : Client host rejected: Access denied -- cgit v1.2.3-1-g7c22 From e9e2bd6e3d5ab451e7b74d1f9b0ff256f973f5b8 Mon Sep 17 00:00:00 2001 From: it33 Date: Wed, 14 Oct 2015 23:19:53 -0700 Subject: Updating /docs TOC --- doc/README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/README.md b/doc/README.md index 7ee2bb46c..ccb702a5d 100644 --- a/doc/README.md +++ b/doc/README.md @@ -8,15 +8,17 @@ Get up and running quickly with Docker-based install - [AWS Elastic Beanstalk Setup](install/Amazon-Elastic-Beanstalk.md) - [Docker Single Container Preview Setup](install/Docker-Single-Container.md) - [SMTP Email Setup](install/SMTP-Email-Setup.md) +- [System Console Settings](install/Configuration-Settings.md) #### Production Installation Set up Mattermost in your data center - [Software and Hardware Requirements](install/Requirements.md) - [Production Ubuntu Setup](install/Production-Ubuntu.md) - [SMTP Email Setup](install/SMTP-Email-Setup.md) +- [System Console Settings](install/Configuration-Settings.md) #### Configuration and Management -- Configuration Settings Overview +- [System Console Settings](install/Configuration-Settings.md) - [GitLab SSO Configuration](integrations/Single-Sign-On/Gitlab.md) - [Mattermost Release Numbering Scheme](install/Release-Numbering.md) -- cgit v1.2.3-1-g7c22 From feff0e98f52cdf913f03f66b0bdaa844bcb439f4 Mon Sep 17 00:00:00 2001 From: it33 Date: Thu, 15 Oct 2015 06:07:39 -0700 Subject: Update Production-Ubuntu.md --- doc/install/Production-Ubuntu.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/install/Production-Ubuntu.md b/doc/install/Production-Ubuntu.md index 05a56c412..87f8edb84 100644 --- a/doc/install/Production-Ubuntu.md +++ b/doc/install/Production-Ubuntu.md @@ -28,7 +28,7 @@ ## Set up Mattermost Server 1. For the purposes of this guide we will assume this server has an IP address of 10.10.10.2 1. Download the latest Mattermost Server by typing: - * ``` wget https://github.com/mattermost/platform/releases/download/v1.0.0/mattermost.tar.gz``` + * ``` wget https://github.com/mattermost/platform/releases/download/v1.1.0/mattermost.tar.gz``` 1. Unzip the Mattermost Server by typing: * ``` tar -xvzf mattermost.tar.gz``` 1. For the sake of making this guide simple we located the files at `/home/ubuntu/mattermost`. In the future we will give guidance for storing under `/opt`. -- cgit v1.2.3-1-g7c22 From d549d240a8f00ccb19d620a4456c41b48cbe88e2 Mon Sep 17 00:00:00 2001 From: Harrison Healey Date: Thu, 15 Oct 2015 16:16:32 -0400 Subject: Updated node.js source path in Ubuntu dev setup --- doc/developer/Setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/developer/Setup.md b/doc/developer/Setup.md index afaef4ee4..d806b7a9b 100644 --- a/doc/developer/Setup.md +++ b/doc/developer/Setup.md @@ -61,7 +61,7 @@ Any issues? Please let us know on our forums at: http://forum.mattermost.org 3. Reload your bashrc `source ~/.bashrc` 6. Install Node.js - 1. Download the newest version of the Node.js sources from https://nodejs.org/download/ + 1. Download the newest version of the Node.js sources from https://nodejs.org/en/download/ 2. Extract the contents of the package and cd into the extracted files 3. Compile and install Node.js `./configure` -- cgit v1.2.3-1-g7c22 From 50a8e2bd4fa53c6bb2f12a03237be4fbaf259617 Mon Sep 17 00:00:00 2001 From: it33 Date: Thu, 15 Oct 2015 23:18:08 -0700 Subject: Update Troubleshooting.md --- doc/install/Troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/install/Troubleshooting.md b/doc/install/Troubleshooting.md index 8d82100d8..b87663ab3 100644 --- a/doc/install/Troubleshooting.md +++ b/doc/install/Troubleshooting.md @@ -3,5 +3,5 @@ #### Important notes 1. **DO NOT manipulate the Mattermost database** - - In particular, DO NOT delete data from the database, as this will most likely crash Mattermost in strange ways. Mattermost is designed to archive content continously and generally assumes data is never deleted. + - In particular, DO NOT delete data from the database, as Mattermost is designed to stop working if data integrity has been compromised. The system is designed to archive content continously and generally assumes data is never deleted. -- cgit v1.2.3-1-g7c22