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. 03reconmattermost already deployed (containers, volumes, /opt/mattermost)? healthy → verify and skip; never overwrite its data
4. 04reconlocal port 8065 free? is a reverse proxy already on 80/443?
5. 05reconRAM ≥ 2 GB and a few GB of free disk
6. 06actInstall Docker Engine + Compose (only if missing)verify
7. 07actGenerate the secrets (/opt/mattermost/.env)verify
8. 08actWrite /opt/mattermost/compose.yamlverify
9. 09actStart the stackverify
10. 10actThe API respondsverify
11. 11actHTTPS reverse proxy (only if a domain is provided)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. 02verifyGenerate the secrets (/opt/mattermost/.env)Verified bystat -c '%a' /opt/mattermost/.env && grep -c '=' /opt/mattermost/.env
3. 03verifyWrite /opt/mattermost/compose.yamlVerified bydocker compose -f /opt/mattermost/compose.yaml config -q && echo ok
4. 04verifyStart the stackVerified bydocker compose -f /opt/mattermost/compose.yaml ps --status running --format "{{.Service}}"
5. 05verifyThe API respondsVerified bytimeout 180 bash -c 'until curl -s -o /dev/null http://127.0.0.1:8065/api/v4/system/ping; do sleep 5; done'; curl -s -o /dev/null -w '%{http_code}' http://127.0.0.1:8065/api/v4/system/ping
6. 06verifyHTTPS reverse proxy (only if a domain is provided)Verified bycurl -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 Mattermost 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. 05DiscourseDiscourse forum (official discourse_docker install, Let’s Encrypt HTTPS). Takes ports 80/443.