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, version and package manager (apt or dnf)
2. 02reconDocker Engine + compose plugin present and running? (otherwise, docker step)
3. 03reconDiscourse already installed (/var/discourse, app container)? healthy → verify and skip
4. 04reconports 80/443 free? (Discourse takes them whole; taken → stop and report)
5. 05reconRAM ≥ 2 GB (+ swap) and ≥ 10 GB of free disk
6. 06recondoes the domain point to this server? (required for Let’s Encrypt)
7. 07reconactive firewall (ufw or firewalld)? a port is only opened if one is active
8. 08actInstall Docker Engine + Compose (only if missing)verify
9. 09actClone discourse_dockerverify
10. 10actWrite containers/app.ymlverify
11. 11actOpen 80/443 (only if a firewall is active)verify
12. 12actBuild and start (./launcher rebuild app, 10-15 min)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 bysystemctl is-active docker && docker compose version
2. 02verifyClone discourse_dockerVerified bytest -x /var/discourse/launcher && echo ok
3. 03verifyWrite containers/app.ymlVerified bygrep -cE '^\s*(DISCOURSE_HOSTNAME|DISCOURSE_DEVELOPER_EMAILS|DISCOURSE_SMTP_ADDRESS|DISCOURSE_SMTP_PORT|DISCOURSE_SMTP_USER_NAME|DISCOURSE_SMTP_PASSWORD|LETSENCRYPT_ACCOUNT_EMAIL):' /var/discourse/containers/app.yml
4. 04verifyOpen 80/443 (only if a firewall is active)Verified byufw status 2>/dev/null | grep -cE '^(80|443)/tcp'; firewall-cmd --list-services 2>/dev/null; true
5. 05verifyBuild and start (./launcher rebuild app, 10-15 min)Verified bytimeout 270 bash -c 'while systemctl is-active -q discourse-rebuild; do sleep 15; done'; systemctl is-active discourse-rebuild; curl -s -o /dev/null -w '%{http_code}' https://${domain}/

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 Discourse 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 web & cms recipes

1. 01Deploy a Docker Compose appDeploys a (provided) Docker Compose stack, with an HTTPS reverse proxy if a domain is given. Describe your needs in the instructions.
2. 02WordPressWordPress via Docker Compose (app + MariaDB, generated secrets), HTTPS if a domain is provided.
3. 03GhostGhost 6 blogging platform via Docker Compose (Ghost + MySQL), served over HTTPS.
4. 04OdooOdoo 20 Community ERP via Docker Compose (Odoo + Postgres), generated master password, HTTPS if a domain is provided.
5. 05MattermostMattermost team messaging via Docker Compose (Mattermost + Postgres), HTTPS if a domain is provided.