Skip to content

Run it on a server

For: self-hosters moving from the demo to a server other people (or your own phone, or your AI) reach over the internet. At the end: you know the pieces, in the order to set them up, and which page covers each.

The compose kit runs everything on one machine: a small Linux VM (2 vCPU, 2 GiB of RAM is a fine start: Sizing) at home or anywhere. Start from a working install, then add what you need, in this order:

Step Why Page
1. HTTPS and two host names Friends reach the static sites, you reach your page and the shipper reaches /ingest from anywhere, encrypted Put it behind a reverse proxy
2. A login for your page The full view shows everything, other players included Put it behind a reverse proxy
3. Share your page A public site for anyone, a sealed one for friends with the link Share your page
4. Your AI from anywhere claude.ai and ChatGPT call your server from theirs: they need HTTPS and an OAuth login Set up the login for your AI
5. Friends with their own pages Several players, each with their own data, link and AI Add friends
6. Battle.net data (optional) The WoW Token, your look in 3D Battle.net data

Then keep it running:

  • Back up and restore: three volumes and two folders.
  • Upgrade: between versions, and what each release changed.
  • Monitor it: health checks, logs, disk.
  • Harden it: what’s locked down already, and what’s on you.
  • Uninstall: the server, the player’s computer, and the data, separately.

Not using Docker Compose (Kubernetes, Nomad, plain containers)? The same image runs every part: Deploy without compose has the commands, ports and mounts, and Environment variables every setting.