the_icelander

Archiving a channel in Mattermost just sets a flag in the database. Once the bad actor is removed a simple query can restore the channels they archived. Something like: `UPDATE Channels SET DeleteAt = 0 WHERE DeleteAt > [some timestamp]`

There's also a CLI command to restore the channels. While this won't keep it from happening it should get things back to normal fairly quickly.

Not for business, but if you want to get your friends on a chat server it would be easier if they knew you couldn't see everything they said.

My response to someone insisting on using only Microsoft Teams is: What if Teams goes down? How is the IT team going to coordinate bringing it back up? Email? SMS?

Check out the Kubernetes operator, which handles zero-downtime upgrades as well as blue/green deployments and canary builds: https://github.com/mattermost/mattermost-operator

In 5.10 Mattermost added the ability to move the configuration to the database, which solves the issue of having a config.json file. This also has the advantage of versioning your configuration in the database which makes rolling back changes very easy.