@@ -16,17 +16,19 @@ The following instructions deploy Mattermost in a production configuration using
### Requirements
* [docker]
* [docker-compose]
* [docker] (version `1.10.0+`)
* [docker-compose] (version `1.6.0+` to support Compose file version `2.0`)
### Choose Edition to Install
If you want to install Enterprise Edition, you can skip this section.
To install the Team Edition, comment out the following line in docker-compose.yaml file:
```
dockerfile: Dockerfile-enterprise
To install the team edition, comment out the two following lines in docker-compose.yaml file:
```yaml
args:
-edition=team
```
The `app` Dockerfile will read the `edition` build argument to install Team (`edition = 'team'`) or Entreprise (`edition != team`) edition.
### Database container
This repository offer a Docker image for the Mattermost database. It is a customized PostgreSQL image that you should configure with following environment variables :
...
...
@@ -34,6 +36,8 @@ This repository offer a Docker image for the Mattermost database. It is a custom
*`POSTGRES_PASSWORD`: database password
*`POSTGRES_DB`: database name
It is possible to use your own PostgreSQL database, or even use MySQL. But you will need to ensure that Application container can connect to the database (see [Application container](#application-container))
#### AWS
If deploying to AWS, you could also set following variables to enable [Wal-E](https://github.com/wal-e/wal-e) backup to S3 :
*`AWS_ACCESS_KEY_ID`: AWS access key
...
...
@@ -63,8 +67,11 @@ If your database use some custom host and port, it is also possible to configure
If you use a Mattermost configuration file on a different location than the default one (`/mattermost/config/config.json`) :
*`MM_CONFIG`: configuration file location inside the container.
If you choose to use MySQL instead of PostgreSQL, you should set a different datasource :