mattermost / mattermost/docker
Documentation on Mattermost migration
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 533
- Forks
- 284
- PR merge metrics
- No merged PRs in 30d
Description
The documents use the simple export SQL and import SQL process. Also, provide the ways to migrate the files, plugins and configuration from the original mattermost/mattermost-docker repository to the mattermost/docker repository
Prepared
- App built via
mattermost/mattermost-docker - New App built via
mattermost/docker
Steps
- Backup and dump the sql from the original
mattermost/mattermost-dockerPostgres service. - Enable the new Postgres service from the
mattermost/docker. - Import the dumped SQL file into the Postgres service of
mattermost/docker. - Copy the matched volumes folder from the original
mattermost/mattermost-dockerto themattermost/dockervolumes folder. - Restart the app from the
mattermost/dockerversion - Check the
config.jsonand the settings.
Backup and dump the sql from the original mattermost/mattermost-docker version
- Enable the Postgres service from the original
mattermost/mattermost-docker
docker-compose up -d db
- Dump from the original Postgres service.
docker exec -it mattermost-docker_db_1 pg_dump mattermost -U mmuser --no-privileges > dump.sql
Enable the new Postgres service from the mattermost/docker
- Enable the Postgres service from
mattermost/docker.
docker-compose up -d postgres
- Remove the database and create a new one
docker exec -it postgres_mattermost dropdb mattermost -U mmuser
docker exec -it postgres_mattermost createdb mattermost -U mmuser
Import the dumped SQL file into the Postgres service of mattermost/docker
- Copy the
dump.sqlinto the currentmattermost/dockerfolder - Import the dump SQL into the new database
docker exec -i postgres_mattermost psql -U mmuser -d mattermost < dump.sql
Copy the matched volumes folder from the original mattermost/mattermost-docker to the mattermost/docker volumes folder
- COPY
mattermost-docker/volumes/app/mattermost/TOdocker/volumes/app/mattermost - Change the
client-pluginsfolder toclients/plugins
mv client-plugins clients/plugins
- Change the permission and owner
sudo chown -R 2000:2000 volumes
Restart the app from the mattermost/dockerversion
restart the app using the following command in mattermost/docker folder
sudo docker-compose -f docker-compose.yml -f docker-compose.nginx.yml up -d
Check the config.json and the admin settings.
Because of the SiteURL configuration and ListenAddress configuration in mattermost/docker are different from the original mattermost-docker version.
Therefore, please make sure the SiteURL and the ListenAddress matching the new environment or the mattermost service in mattermost/docker might not be enabled correctly.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the migration steps and the referenced docker-compose.yml, docker-compose.nginx.yml, config.json, and volumes paths. Check that the documentation covers SQL backup and restore, volume and plugin moves, ownership, and SiteURL and ListenAddress updates. Done means a newcomer can follow the commands to migrate the database, files, plugins, and configuration to mattermost/docker.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, postgresql, shell
- Domain
- databases, devops, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100