Neel
Patel

Managing several game servers meant juggling SSH sessions and terminal windows for every restart, command, and health check.

I built a web dashboard that controls all of them from one place.

• A Flask backend exposes REST endpoints for authentication, server control, and live metrics.
• JWT authentication and separate profiles keep each server's configuration and access isolated.
• Python modules use Paramiko to run remote SSH commands and stream server health back to a React front end.
• The whole app is deployed on Oracle Cloud, next to the servers it manages.

Two cloud servers with an active player base, running around the clock, with nobody else to call when something breaks.

• Wrote auto-restart scripts and nightly automated backups so crashes recover without me stepping in.
• Tracked down lag and crash incidents with a profiler, found the causes, and tuned JVM settings to fix recurring slowdowns.
• Recovered corrupted player data after a server failure.
• Set up persistent firewall rules with iptables to lock down outside access.
• Noticed an unexpected storage charge on the cloud bill, traced it to how the disk was provisioned, and migrated everything to a new instance to stop it.

A four-project sequence on a single codebase. Each stage added new requirements, so the work was as much about refactoring and design as writing features.

Every stage included formal design documentation and a written test plan, which I then ran against the implementation to verify behavior.

A game simulation built in three phases. It uses a polymorphic event system to model different plays through a shared interface, recursive reporting to summarize possessions, and manual memory management throughout.