design principles:
- mattermost has seperate data-directory to seperate code from data (symlinks are used) version upgrade possible (just increase the version-number, decrease might not work due db upgrades)
- nginx with custom mattermost config as reverse proxy in front of mattermost
- highly re-useable with template-override
- db creation is out-if-scope (see example playbook)
TODO:
- Backup before installing new version?
none
see mattermost-example-playbook.yml.
GPLv3
Sven Holter Stefan Schwarz