Better handling of server config with updates

I run a private server for some friends, and because we like the latest updates (and beta tends to be just about as stable as release in my experience, crash-wise) we use Beta version. This causes the server update process to be much more frequent, and the config file gets wiped out every update. I have a basic (and potentially brittle) bash script to re-configure the config file but it would be nice if updating the server didn't wipe out the config.

Possible solutions off the top of my head:

- Ship a 'default config' file and the server startup process will copy that into being the actual config file as the very first action if the actual config file doesn't exist yet
- Some system where the launcher update process doesn't overwrite the server config file when extracting the new files
- Some kind of more OS-level storage of the server config, similar to the client's config (as long as it's still easy to set up by hand for headless servers)