Discussion
A note regarding the small web:
“I’m not using a Dockerfile for the instructions, because when you’re using the cheapest virtual private server (VPS) offerings, your disk space limits are really tight and docker eats space like crazy, so this guide does not require docker.”
⇒ https://www.draketo.de/software/enter-three-witches#webservice
@vampirdaddy I don’t know enough systemd to answer that – and don’t want to depend on it in the tutorial (though it is available in debian by default).
If I could and if you have instructions to make that easy (including updates by restarting via SSH and multiple processes – I have plans for zero downtime updates) I’d be happy if you could send me pointers for an optional step that secures it more …
@ArneBab
Still working on a bumpless setup myself.
Also thinking about migrating to *BSD-based webservers.
@vampirdaddy my plan is to tell nginx to drain the connection (avoid sending more people to the backend service) and to add a command to the game that causes it to shut down once the last player left. And then start again, By pre-compiling the updated version, that only gives a few seconds of downtime which should not be visible to the outside (since all players play on the other instance).
Sadly in non-enterprise nginx that means I need to script the nginx API. But I still think I can do it.
Install Fedizen
Get the full app experience
@ArneBab
You still could place them in an systemd-nspawn container/jail?