Proper way to backup/restore config

[mattermost]

Proper way to backup/restore config

[Szymongib]

@nicolas-goudry Config in the database is the correct way. Mattermost Operator uses it by default as Operator sets MM_CONFIG based on the database configuration. Unless you want to use a different database for config, explicitly setting MM_CONFIG is not necesarry.

In regards to config in volumes, I do not think using ConfigMap is possible as ConfigMap can only be mounted as read-only while config can be changed from System Console. We also do not recommend using volumes with config.json as this is not really a tested solution.

[nicolas-goudry]

As of my understanding, there is three ways to handle this:

1. via configMap:
   • create a configMap with environments variables corresponding to desired configuration
   • set all variables in installation manifest with valueFrom.configMapKeyRef
2. via volumes and volumeMounts:
   • create a configMap from config.json file
   • create a volume from this configMap
   • create a volumeMount of this volume
   • set MM_CONFIG environment variable to point to mounted file path
3. via database:
   • set MM_CONFIG to database connection string

Please correct me if I’m wrong.

I’ll use the database stored configuration, effectively allowing backup/restore from database backup/restore process. Closing this now (sorry for the useless noise).