**Status: today this is a manual, ops-level process — a packaged one-click VPS installer is still
a backlog item**, not shipped yet. If you're comfortable with Docker Compose and a Linux server,
the pieces below are real and already used to run the hosted agentplayground.net production
instance; there just isn't a friendly wizard around them yet.

The full-stack docker-compose.yml at the repo root runs the app behind Traefik (automatic
HTTPS via Let's Encrypt) alongside PostgreSQL + pgvector, Redis, and optionally n8n and Ollama —
see .env.template for every variable it needs (domain, ACME email, database credentials, and so
on) and Environment variables reference for the highlights.

Rough shape of a manual deploy:

1. Point DNS at your server (an A record for your root domain, plus a wildcard * record for subdomains like app.yourdomain.com, n8n.yourdomain.com).
2. Copy .env.template to .env, fill in DOMAIN, ACME_EMAIL, generate the secrets it asks for (openssl rand -hex 32 for most of them).
3. docker compose -f docker-compose.yml -f docker-compose.prod.yml up -d --build.
4. Traefik requests and renews HTTPS certificates automatically once DNS resolves.

Deploys to an already-running server are done by copying changed files over (scp), not
git pull on the server — this project's own hosted instance is deployed this way deliberately.

A packaged, scripted VPS install path — docker/docker-compose.vps.yml (a leaner overlay: Traefik
+ Let's Encrypt + your real domain, registration closed by default) plus an scripts/install-vps.sh
that walks through DNS/env setup interactively — is on the roadmap but doesn't exist yet. Until
then, deploying to your own server means reading .env.template and docker-compose.yml
directly and adapting them, not running a single installer command.

• Docker install (desktop) — the supported, packaged path if you don't need your own domain/server
• Environment variables reference