Just used this guide to set up Luanti on a VPS via Docker. It worked beautifully and made things pretty easy.
I think my biggest complaint had nothing to do with this guide. It was how counterintuitive it was to get the world set up with Mineclonia. The file based configuration is very Linux-y and I was expecting more GUI-based config.
The nice thing about it being a configuration file is that you can back it up together with the
docker-compose.yml. Professional sysadmins would put it into a Git repo. If you need to set the server back up, you just clone the repo onto the target machine and run thedocker composecommand and it should set everything back up as it should be. 🙂Are there any concerns about committing the SQLite db files into git? Won’t using git to back those up regularly eventually make the repository history extremely large?
Oh yeah, I didn't mean to check in the SQLite database file, just the configuration file and the
docker-compose.yml.
Git cannot diff binary files, so every version of your SQLite database would be checked into the history in full and all of them would get downloaded when you do agit clone. Theoretically, you could get around this with Git LFS, but it just doesn't make a whole lot of sense to put the SQLite database into Git. You don't iterate on the database in a way that would warrant commits. In particular, you wouldn't want to roll back the database, if you're rolling back something in your configuration file. I also imagine the SQLite database would contain usernames and passwords, so you definitely don't want that in a potentially public Git repo.So, yeah, you want a separate backup mechanism for the SQLite database. You could put the way this backup tool is rolled out into the
docker-compose.yml, but yeah, that's somewhat more advanced than this Luanti deployment.