Now users should create a symbolic link to docker-compose-ssl.yml if they want to enable SSL or docker-compose-nossl.yml if not. Rewrite README to describe this rule. This fixes https://github.com/mattermost/mattermost-docker/issues/5.
1.7 KiB
Dockerfiles for Mattermost in production
Requirement
Installation
Install with SSL certificate
-
Create a symbolic link
docker-compose.yml
todocker-compose-ssl.yml
:ln -s docker-compose-ssl.yml docker-compose.yml
-
Put your SSL certificate as
web/cert/cert.pem
and the private key that has no password asweb/cert/private/key-no-password.pem
. If you don't have them you may generate a self-signed SSL certificate. -
Build and run mattermost
docker-compose up -d
-
Open
https://your.domain
with your web browser.
Install without SSL certificate
-
Create a symbolic link
docker-compose.yml
todocker-compose-nossl.yml
:ln -s docker-compose-nossl.yml docker-compose.yml
-
Build and run mattermost
docker-compose up -d
-
Open
http://your.domain
with your web browser.
Starting/Stopping
Start
docker-compose start
Stop
docker-compose stop
Removing
Remove the containers
docker-compose stop && docker-compose rm
Remove the data and settings of your mattermost instance
sudo rm -rf volumes
Known Issues
- Do not modify the Listen Address in Service Settings.
- Rarely 'app' container fails to start because of "connection refused" to database. Workaround: Restart the container.
More informations
If you want to know how to use docker-compose, see the overview page.
For the server configurations, see prod-ubuntu.rst of mattermost.