Where Does LinuxGSM Store Game Servers?
LinuxGSM keeps per-server instances under user home directories with configs beside each install. Back up serverfiles and configs per game server.
Last updated
LinuxGSM organizes game servers as instances under a service user home. Each instance holds its serverfiles, configs, logs, and backups in one directory tree, managed by the lgsm scripts. Common functions live in the shared LinuxGSM directory.
That per-instance layout makes single-server backups trivial and full-host moves mechanical. Monitor disk per instance since game updates balloon unpredictably. Keep firewall ports per game documented with the instance; rebuilds forget them otherwise.
Where LinuxGSM stores this, by platform
~/lgsm/
Per-server directories with configs and serverfiles together. Back up per instance with the server stopped. Fix ownership to the service user after restores.
Frequently asked questions
How do I migrate a LinuxGSM server?
Stop the server, archive its directory with configs and serverfiles together, then restore to matching paths on the new host. Fix ownership to the service user afterward. Database-backed games need their database dumps alongside the files.
How do updates work?
Run the installer per game server; shared modules update centrally while instances stay separate. Test one low-risk server first after major updates. Configs in instance directories survive module updates untouched.
Notice an outdated path? Let us know.