Bending ejabberd to behave like a 12factor app about docker-ejabberd HOT 4 CLOSED

This is great. I think a run-script is a good point to start with. We also can use that script to i.e. share the erlang cookie over etcd or set the hostname to cluster ejabberd instances.

I also like your idea to parse the config file with Jinja2. Setup the admin user with password could be another good run-time configuration. @swvitaliy addressed this in swvit-dl@9dfefa7.

Other interesting forks we maybe can merge from:

• https://github.com/jprjr/docker-ejabberd
• https://github.com/olragon/docker-ejabberd

I will read the 12factor document to get a better idea. And merge your requests later this day.

from docker-ejabberd.

erlang cookie from etcd

My preference would be to leave this out of the image in a tool which orchestrates the containers and passes this in as an environment variable. Happy to have the run script set the cookie at runtime from the environment variable, though. I'll submit a PR for that.

Setup the admin user with password

This opens some extra questions about clustering and persistence of state. I'll stay away from this for the moment.

from docker-ejabberd.

Logging to stdout inclusive extra logfiles, done.
Graceful shutdown on SIGTERM and SIGINT, done.
Config in the runtime environment, done.

Please re-open if you do not agree.

from docker-ejabberd.

Awesome, thanks for all of that work @rroemhild and sorry I couldn't free myself up to contribute more recently.

from docker-ejabberd.