Skip to main content

Deployment recipes

Every recipe here is the same two files and the same command. You generate a .env and a docker-compose.yml from the setup builder, drop them in a folder, and run docker compose up -d. What changes from one recipe to the next is host-specific: where the data lives, how the box is reached, and how HTTPS is terminated.

Install is the full walkthrough and the place to start. These pages are the short, host-specific notes on top of it. Pick the one that matches your setup:

RecipeWhen it fits
Single boxOne machine runs everything. The default.
Raspberry PiA Pi 4 or 5 for a household or yourself.
Behind a reverse proxyYou already run nginx, Traefik, or Caddy for TLS.
External databaseYou want to use a Postgres you already run.
Tailscale onlyPrivate access with real HTTPS and nothing exposed.

The recipes are not exclusive. A Raspberry Pi behind your existing reverse proxy, pointed at an external Postgres, is three of these at once. Read the pages that apply and combine the .env changes.