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.

1. 01recondistro and version: apt (Debian/Ubuntu) or dnf (RHEL/Fedora/Rocky/Alma)?
2. 02reconDocker Engine + compose plugin present and service active? (podman-docker or snap Docker: report it, do not mix)
3. 03reconuptime-kuma already deployed (container, volumes, /opt/uptime-kuma)? healthy → verify and skip; never overwrite or delete
4. 04reconport 3001 (or the one from the port variable) already taken, and by what? empty = free; taken → ask for another port (ask_user)
5. 05reconis /opt on a local disk? (NFS/CIFS are not supported for Kuma data)
6. 06recononly if a domain is provided: is a reverse proxy already on 80/443? (reuse it rather than installing a second one)
7. 07reconis a firewall (ufw or firewalld) active?
8. 08actInstall Docker Engine + Compose (only if missing)verify
9. 09actWrite /opt/uptime-kuma/compose.yamlverify
10. 10actStart the stackverify
11. 11actResponds over HTTPverify
12. 12actInstall Caddy (only if a domain is provided and no reverse proxy)verify
13. 13actHTTPS reverse proxy (only if a domain is provided)verify
14. 14actOpen 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.

1. 01verifyInstall Docker Engine + Compose (only if missing)Verified bydocker compose version && systemctl is-active docker
2. 02verifyWrite /opt/uptime-kuma/compose.yamlVerified bycd /opt/uptime-kuma && docker compose config --quiet && echo ok
3. 03verifyStart the stackVerified bydocker inspect -f '{{.State.Status}}' uptime-kuma
4. 04verifyResponds over HTTPVerified bycurl -s -o /dev/null -w '%{http_code}' --retry 20 --retry-delay 5 --retry-connrefused http://127.0.0.1:${port}/
5. 05verifyInstall Caddy (only if a domain is provided and no reverse proxy)Verified bycaddy version && systemctl is-active caddy
6. 06verifyHTTPS reverse proxy (only if a domain is provided)Verified bycurl -s -o /dev/null -w '%{http_code}' --retry 6 --retry-delay 5 https://${domain}/
7. 07verifyOpen 80/443 (only if a domain is provided and a firewall is active)Verified byufw 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.

SEC.04

Variables

What you choose before launching — the recipe fills in the rest.

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.

SEC.06

Deploy on Servor button

Maintain Uptime Kuma 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

1. 01VaultwardenVaultwarden password manager (Bitwarden-compatible) via Docker Compose, over HTTPS when a domain is provided.
2. 02GiteaLightweight Gitea Git forge via Docker Compose (SQLite), web on localhost, Git SSH on a dedicated port.
3. 03NextcloudNextcloud (file cloud) via Docker Compose: PostgreSQL, Redis, cron, admin created automatically.
4. 04JellyfinJellyfin media server via Docker Compose, media folder mounted read-only, HTTPS when a domain is provided.
5. 05n8nn8n workflow automation via Docker Compose, over HTTPS with webhooks when a domain is provided.