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. 01reconAre Docker + Compose present? (otherwise install them first)
2. 02reconWhich containers/ports are already running?
3. 03actPrepare the folder + composeverify
4. 04actStart the stackverify

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. 01verifyPrepare the folder + composeVerified bytest -f /opt/app/compose.yml && docker compose -f /opt/app/compose.yml config -q && echo ok
2. 02verifyStart the stackVerified bydocker compose -f /opt/app/compose.yml ps -q --status running | wc -l

SEC.03

Variables

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

SEC.04

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.05

More web & cms recipes

1. 01WordPressWordPress via Docker (app + MariaDB), ready to configure.
2. 02GhostGhost blogging platform via Docker.
3. 03OdooOdoo Community ERP via Docker (app + Postgres).
4. 04DiscourseDiscourse forum (official install). Destructive: takes 80/443.
5. 05MattermostMattermost team messaging via Docker Compose.