Replies: 3 comments
-
I prefer not to run additional processes inside of the container. The automation you described can be performed by a sidecar container via rcon. |
Beta Was this translation helpful? Give feedback.
0 replies
-
That's understandable, I might see if I can make a sidecar container to do that |
Beta Was this translation helpful? Give feedback.
0 replies
-
You might be able to draw some inspiration from the mc-backup container since it has similar cross container rcon interactions https://github.com/itzg/docker-mc-backup/blob/master/scripts/opt/backup-loop.sh |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Enhancement Type
Improve an existing feature
Describe the enhancement
Currently when adding players to the whitelist file provided to the
WHITELIST_FILE
environment variable the change isn't reflected till the container restarts which kinda sucks because to whitelist new players you have to basically kick any currently logged in players.I propose using something akin to incrond to monitor changes in the whitelist file provided to the
WHITELIST_FILE
environment variable and when a change is detected running the relevant script based on theEXISTING_WHITELIST_FILE
environment variable then sending an rcon command the server to reload the whitelist.Beta Was this translation helpful? Give feedback.
All reactions