Reboot cron job

[Dashboy1998]

Context

• Adds a cron job to automatically reboot the server as mentioned in Restart Container to Stop Memory Leaks #259

Choices

• Already using cron for automatic updates and backups

Test instructions

1. Enable rcon & auto reboots
2. Set the reboot expression near your current time so you don't wait long
3. Start the container
4. Join the game and wait for the reboot

Checklist before requesting a review

• I have performed a self-review of my code
• I've added documentation about this change to the README.
• I've not introduced breaking changes.

[Technetium1]

Could be nice to add in https://github.com/thijsvanloef/palworld-server-docker/blob/main/.env.example

[MSpreckels]

Dont we already have a reboot cronjob? #206

[Dashboy1998]

Dont we already have a reboot cronjob? #206

That appears to be specifically for Kubernetes whereas this will work for the stand alone container.

[MSpreckels]

You are correct. Does it make sense to keep the k8s only variant of a daily reboot when it will be implemented in the container?

[Dashboy1998]

You are correct. Does it make sense to keep the k8s only variant of a daily reboot when it will be implemented in the container?

I think the k8s version has some specific benefits for k8s. I don't use k8s so I'm not really sure of the benefits of having a separate solution for them.

[thijsvanloef]

LGTM

[Technetium1]

@MSpreckels keeping both makes sense to me because they are not restarting exactly the same way. There's more granularity available with the Kubernetes spec, such as killing the job if it times out, and the fact that prevents concurrent jobs from executing at once, but the same effect is unnecessary with only 1 Docker container. Even moreso because there's potential for that job to run on multiple replicas in a cluster (even if they don't exist right now); with offset times, or just waiting for completion on each replica.

Worth noting that AUTO_REBOOT_ENABLED=false to prevent issue for k8s users.