This issue is closely related to the Issue #27
Using the SOAP interface, it should be possible to gracefully shut downthe server via a request.
This will notify all players with an in-game warning message that the server will be shut down shortly.
How to integrate this functionality healthy with the standard lifecycle of a container Docker?
Should it intercept a SIGTERM signal and behave accordingly?
Is this not a viable way, since Docker timeout what will emit a SIGKILL signal after a while?
Should it be -for this reason- a separate command, simply available in the entrypoint.sh script?
Needs some investigations... 🤔
This issue is closely related to the Issue #27
Using the SOAP interface, it should be possible to gracefully shut downthe server via a request.
This will notify all players with an in-game warning message that the server will be shut down shortly.
How to integrate this functionality healthy with the standard lifecycle of a container Docker?
Should it intercept a
SIGTERMsignal and behave accordingly?Is this not a viable way, since Docker timeout what will emit a
SIGKILLsignal after a while?Should it be -for this reason- a separate command, simply available in the
entrypoint.shscript?Needs some investigations... 🤔