The catalog
Adding a game server means picking a type from the catalog and answering a small number of questions - port, memory limit, version. The panel installs the required runtime, creates the instance user, writes the systemd unit and starts the server.
Java-based servers get the right JDK version installed if it is missing. Source-engine servers get SteamCMD and the required 32-bit libraries. This is the part that consumes an afternoon when done by hand.
Resource limits
Each instance runs in its own systemd slice with CPU quota, memory limit and task limit. A Minecraft server that decides to allocate everything cannot take the web sites down with it, which is the entire reason for running limits rather than trusting configuration files.
Disk quotas are per instance user, and the panel warns before an instance hits its allocation rather than after.
Operations
- Live console with command input and searchable scrollback
- Start, stop, restart and kill with a graceful timeout
- Scheduled restarts with in-game warnings where the server supports them
- Scheduled backups with retention
- File manager and SFTP access scoped to the instance directory
- Port allocation tracked by the panel to avoid collisions
Backups
Backups run on a schedule per instance, with configurable retention and an option to stop the server for a consistent snapshot or take a live copy. Restores are a one-click operation from the panel with the previous state kept until the restore is confirmed working.