Operations Guide¶
This section covers deploying, configuring, and running HoloMUSH servers.
Overview¶
HoloMUSH is designed to be easy to deploy and operate. It runs as a single binary with PostgreSQL as its only external dependency.
Getting Started¶
- Quick Start - Get a development server running in minutes
- Production Setup - Deploy with proper security and monitoring
- Configuration - Customize behavior for your use case
Documentation Sections¶
Deployment¶
- Quick Start - Run HoloMUSH locally for development
- Production Deployment - Deploy to Kubernetes or bare metal
- Docker - Container images and compose files
Configuration¶
- Server Configuration - All configuration options
- TLS Setup - Secure connections with certificates
- Database Setup - PostgreSQL configuration
Operations¶
- Monitoring - Prometheus metrics and Grafana dashboards
- Backup & Recovery - Data protection strategies
- Scaling - Horizontal scaling considerations
Security¶
- Security Hardening - Best practices for production
- Authentication - Player authentication options
- Access Control - ABAC policy configuration
Requirements¶
| Component | Minimum | Recommended |
|---|---|---|
| CPU | 1 core | 2+ cores |
| Memory | 256 MB | 512 MB |
| PostgreSQL | 18+ | 18+ |
| Storage | 1 GB | 10+ GB |
Telnet vs Web¶
HoloMUSH supports two connection methods:
- Telnet (port 4201) - Classic MU* client compatibility
- WebSocket (port 8080) - Modern web client with PWA support
Both protocols connect to the same game world and share the same session system.