Not Official
Surviving Chernarus is hard. Deploying your server shouldn't be.
End-to-end automation for running a self-hosted DayZ dedicated server on Proxmox — provisioned with OpenTofu, configured with Ansible, secrets kept in 1Password. A dedicated observability container captures server metrics and logs, surfaced through Grafana.
Built for Proxmox home-lab setups first, with a roadmap toward cloud providers.
┌──────────────────────────────────────────────────────┐
│ Proxmox Host │
├──────────────────────────────────────────────────────┤
│ ┌──────────────────────┐ ┌──────────────────────┐ │
│ │ Game Server VM │ │ Observability LXC │ │
│ ├──────────────────────┤ ├──────────────────────┤ │
│ │ DayZ DS │──▶│ Loki │ │
│ │ node_exporter ───┼──▶│ Prometheus │ │
│ │ Promtail │ │ Grafana │ │
│ └──────────────────────┘ └──────────────────────┘ │
└──────────────────────────────────────────────────────┘
The game server runs the DayZ dedicated server process alongside two lightweight exporters: node_exporter (system metrics) and Promtail (log shipping). A separate Proxmox LXC container runs the full observability stack. Nothing from monitoring is installed on the game server.
| Layer | Tool |
|---|---|
| Provisioning | OpenTofu (Terraform-compatible) |
| Configuration | Ansible |
| Secrets | 1Password (op run) |
| Hypervisor | Proxmox VE |
| OS | Debian 13 (cloud image / LXC template) |
| Game Server | DayZ Standalone (Steam App 223350) |
| Metrics | Prometheus + node_exporter |
| Logs | Loki + Promtail |
| Visualization | Grafana |
make init -> initialise OpenTofu backend
make plan -> preview infrastructure changes (dry run)
make provision -> create VM + LXC
make refresh -> re-read state without infrastructure changes
make inventory -> write Ansible inventory from Terraform outputs
make galaxy -> install Ansible Galaxy collections (one-time)
make configure -> run Ansible: baseline, game server, telemetry, monitoring
make steamcmd-auth -> pre-authenticate SteamCMD if Steam Guard is enabled
make destroy -> tear down all infrastructure
First time here: docs/GUIDE.md covers what self-hosting means, prerequisites, Proxmox setup, secrets configuration, and the full deployment sequence.
Day-to-day operations, configuration reference, and common commands: docs/OPERATIONS.md.
Problems: docs/TROUBLESHOOTING.md.
- Phase 1 — Game server: DayZ DS, SteamCMD, systemd service, UFW
- Phase 2 — Observability: Proxmox LXC, Loki, Prometheus, Grafana, Promtail
- Phase 3 — Dashboards and tuning: Grafana panels, DayZ log parsing, map and difficulty configuration, mod automation, maintenance commands
- Phase 4 — Provider abstraction: Hetzner, OVH, Vultr, and other VPS providers
Licensed under the MIT License.