Kyâne Pichou

I'm not sure that there is a typical way to handle this.I look at some other popular free softwares (eg. [Etherpad](https://github.com/ether/etherpad-lite/wiki/How-to-put-Etherpad-Lite-behind-a-reverse-Proxy), [Rocket Chat](https://github.com/RocketChat/Rocket.Chat/blob/develop/docker-compose.yml), [Mastodon](https://github.com/tootsuite/mastodon/blob/master/docker-compose.yml)) and they generally provide a docker...

I don't understand what you want to do, but it doesn't seems to be Docker related ^^

I agree that having a health check command directly in Mattermost could be interesting, but your workaround with the `ENV` directive seems ok to me.

I agree it could be a good idea, but I don't know if we can do this with the Docker Hub auto-build from the Github repository.

Could be great, I don't have the access to configure Github/Docker Hub hooks for the repository. Maybe @cpanato can ?

I think you didn't set correct permissions for your volumes => https://github.com/mattermost/mattermost-docker#start

I think we should keep Host mounted volumes on the `docker-compose.yml` file, it could be a breaking change to lot of people if we change this behavior. Also, it allow...

@xcompass What do you think about this ? I didn't like the idea to have multiple `docker-compose.vX.yml` file because it can confused people. But maybe I'm wrong about this and...

Moving to Docker volumes is a big changes for current users and I kind of like bindings since it is easy to backup/modify your data (eg. Mattermost `config.json` file). But...

I keep this issue opened but in standby for the moment. We will probably change our repository organization with PR#195. We will probably add Docker volumes features to the new...