Self-Hosting Rakazo on Dokploy with Docker Compose
By Royan Gagas
Rakazo ships an installer that writes its own .env and runs Docker Compose on a bare host. That is fine until the box already runs Dokploy — same Traefik, same TLS, same deploy button — and you want Rakazo to be one more service in that panel instead of a second, parallel universe of containers.
This course is that version: the published GHCR images, Postgres, the sandbox supervisor, the API, the worker, and one disposable computer container per chat thread — wired into a Dokploy Compose service, routed through dokploy-network on port 5173, with the single Dokploy setting that silently deletes your computer image at 23:50 every night turned off.
What you need
- A VPS with Docker Engine 26+ (API 1.45+) and the Compose plugin. Dokploy already installs this.
- A domain you can point at the box.
- One model key (OpenRouter, or any provider you already pay for).
What you get
- A paste-ready
compose.yamlwith every service, network and volume explained — not just copied.
- The full secret list, how to generate each value, and which ones can never be rotated without data loss.
- A working HTTPS origin on
web:5173, with the four URL variables that break cookies and CORS when they disagree.
- A day-2 playbook: upgrades by image tag, a restore drill that actually restores, and the failures I hit first.
Format: text lessons with real files and real commands. No video, no hand-waving.
Stack: Docker Compose · Dokploy · Traefik · Postgres 16 · Node/TypeScript