SEC.01
The playbook
The run starts read-only: the recon probes decide what happens next. The steps that follow are adapted to the distribution and state found — a real machine is rarely clean.
- 01recondistro and version: apt (Debian/Ubuntu) or dnf (RHEL/Fedora/Rocky/Alma)?
- 02reconDocker Engine + compose plugin present and service active? (podman-docker or snap Docker: report it, do not mix)
- 03reconimmich already deployed (container, volumes, /opt/immich)? healthy → verify and skip; never overwrite or delete
- 04reconport 2283 (or the one from the port variable) already taken, and by what? empty = free; taken → ask for another port (ask_user)
- 05reconfree RAM, CPU and disk: Immich wants ≥ 4 GB of RAM (6 recommended), 2 cores, and disk for the photos
- 06recon/opt on a local disk? (the Postgres database does not support network shares)
- 07recononly if a domain is provided: is a reverse proxy already on 80/443? (reuse it rather than installing a second one)
- 08reconis a firewall (ufw or firewalld) active?
- 09actInstall Docker Engine + Compose (only if missing)verify
- 10actDownload the official compose and .envverify
- 11actConfigure the .env (paths, time zone, generated DB password)verify
- 12actRestrict the web port to 127.0.0.1verify
- 13actStart the stackverify
- 14actResponds over HTTPverify
- 15actInstall Caddy (only if a domain is provided and no reverse proxy)verify
- 16actHTTPS reverse proxy (only if a domain is provided)verify
- 17actOpen 80/443 (only if a domain is provided and a firewall is active)verify
SEC.02
What it verifies
Each step ships its own check. The run only moves on when the check passes, so what the recipe reports as done is what is actually on the server.
- 01verifyInstall Docker Engine + Compose (only if missing)Verified by
docker compose version && systemctl is-active docker - 02verifyDownload the official compose and .envVerified by
grep -c "immich-server" /opt/immich/docker-compose.yml && grep "^IMMICH_VERSION=" /opt/immich/.env - 03verifyConfigure the .env (paths, time zone, generated DB password)Verified by
grep -E "^(UPLOAD_LOCATION|DB_DATA_LOCATION|TZ)=" /opt/immich/.env; grep -c "^DB_PASSWORD=postgres$" /opt/immich/.env - 04verifyRestrict the web port to 127.0.0.1Verified by
grep -c "127.0.0.1:${port}:2283" /opt/immich/docker-compose.yml - 05verifyStart the stackVerified by
docker inspect -f '{{.State.Status}}' immich_server - 06verifyResponds over HTTPVerified by
curl -s -o /dev/null -w '%{http_code}' --retry 40 --retry-delay 5 --retry-connrefused http://127.0.0.1:${port}/api/server/ping - 07verifyInstall Caddy (only if a domain is provided and no reverse proxy)Verified by
caddy version && systemctl is-active caddy - 08verifyHTTPS reverse proxy (only if a domain is provided)Verified by
curl -s -o /dev/null -w '%{http_code}' --retry 6 --retry-delay 5 https://${domain}/ - 09verifyOpen 80/443 (only if a domain is provided and a firewall is active)Verified by
ufw status 2>/dev/null | grep ALLOW; firewall-cmd --list-ports 2>/dev/null; true
SEC.03
Guardrails
Non-negotiable instructions the run must respect, whatever it finds on the server.
Immich already running → verify and report, recreate nothing. Never regenerate the DB_PASSWORD of an existing database. Never delete /opt/immich/library or /opt/immich/postgres. Listens on 127.0.0.1; HTTPS when a domain is provided. Create the admin account on first access (the first visitor creates it). Read the release notes before bumping IMMICH_VERSION.
SEC.04
Variables
What you choose before launching — the recipe fills in the rest.
| Name | Meaning |
|---|---|
| ${domain} | Domain (optional, enables HTTPS) |
| ${port} | Local port (127.0.0.1) |
| ${tz} | Time zone |
SEC.05
How a recipe runs in Servor
Servor is zero-knowledge: the platform cannot execute anything on its own. When you launch this recipe, a run reads the reconnaissance, plans the steps and asks for your approval. Each approved command is signed by your browser — with a key the server never sees — then relayed verbatim to the agent, which verifies the signature locally before executing.
search by intent — type “firewall”, get ufw
- 01Read-only reconnaissance before any change
- 02Every command signed by your browser, approved by you
- 03Each step verified before the run moves on, every run kept in the history
SEC.06
Deploy on Servor button
Maintain Immich or a project that needs it? Put this button in your README or on your site: one click and your users install it on their own server.
SEC.07
More self-hosted recipes
- 01VaultwardenVaultwarden password manager (Bitwarden-compatible) via Docker Compose, over HTTPS when a domain is provided.
- 02GiteaLightweight Gitea Git forge via Docker Compose (SQLite), web on localhost, Git SSH on a dedicated port.
- 03Uptime KumaUptime Kuma 2 uptime monitoring via Docker Compose, over HTTPS when a domain is provided.
- 04NextcloudNextcloud (file cloud) via Docker Compose: PostgreSQL, Redis, cron, admin created automatically.
- 05JellyfinJellyfin media server via Docker Compose, media folder mounted read-only, HTTPS when a domain is provided.
Verified recipe
Run this recipe on your server
Connect a server, launch the recipe, and approve each step as Servor executes and verifies it. Free plan, no card required.