Overview
Game Server Deployment Manager is a web tool for my VPS. It installs and manages separate Minecraft servers from one interface.
I built it to replace repeated command-line setup. The tool keeps each server, world, settings, and backup separate.
What I built
- Added deployment for vanilla, modded, and plugin-based servers
- Added server start, stop, restart, and live status controls
- Added player lists, operator access, whitelist controls, and server settings
- Added automatic port selection and server addresses
- Added scheduled backups, manual backups, restore controls, and retention settings
- Added modpack and plugin updates with validation
- Added server cloning and reusable templates
- Added logs and safe editing for supported configuration files
- Added scheduled starts, restarts, and idle actions
Approach
Each Minecraft server runs in its own Docker container. The manager validates settings before it changes a deployment. It also limits file access to supported server files.
Backups run before high-risk changes. If a modpack contains a client-only file, the deployment can exclude that file and keep the rule for later updates.
Outcome
The manager lets me create and maintain several Minecraft servers without repeating the full setup process. It also gives me a safer way to update, repair, and restore a server.
This project taught me to design for long-running operations and partial failures. A deployment tool must show clear progress, protect existing data, and keep recovery steps available.