processone / ejabberd

Robust, Ubiquitous and Massively Scalable Messaging Platform (XMPP, MQTT, SIP Server)
https://www.process-one.net/en/ejabberd/
Other
6.01k stars 1.5k forks source link

Dockerfile: Include an entrypoint script for ejabberdctl #4071

Closed sando38 closed 11 months ago

sando38 commented 11 months ago

Hi @badlop

The entrypoint script serves as a placeholder, so that admins can replace it with an actual entrypoint script, e.g. for initiating ejabberd clusters, through mounting it to the path /usr/local/bin/run.sh.

This PR does not change anything of the existing functions of the image.

Motivation: I would like to use the image as basis for the helm-chart with these scripts and not rely on a custom image in the end.

coveralls commented 11 months ago

Coverage Status

coverage: 32.991% (+0.007%) from 32.984% when pulling ea157bae9b696f5ef72f62d960a7e97053c9d088 on sando38:master into 20a8654be2eb6575bff0e2d75fbe9216e85b7508 on processone:master.

sando38 commented 11 months ago

Deleted the branch by accident, will open again if necessary.

Neustradamus commented 11 months ago

@badlop, @prefiks, @mremond: @sando38 needs to create a new PR?

sando38 commented 11 months ago

I think, I don't. For my particular case, I discovered two options to override entrypoint and cmd: https://www.ithands-on.com/2021/11/kubernetes-101-overriding-entrypoint.html