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 (apt or dnf) and architecture (amd64/arm64)
  2. 02reconDocker Engine + compose plugin present and daemon active?
  3. 03reconloki container or loki-data volume already present?
  4. 04reconport 3100 free? otherwise who holds it
  5. 05reconfree disk to store logs
  6. 06actInstall Docker Engine (only if missing)verify
  7. 07actStart Loki 3.7verify
  8. 08actLoki is readyverify

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. 01Install Docker Engine (only if missing)Verified bydocker compose version && systemctl is-active docker
  2. 02Start Loki 3.7Verified bydocker inspect -f "{{.State.Running}}" loki
  3. 03Loki is readyVerified bycurl -s -o /dev/null -w '%{http_code}' http://127.0.0.1:3100/ready

SEC.03

Guardrails

Non-negotiable instructions the run must respect, whatever it finds on the server.

Never delete the loki-data volume. Loki has no authentication: it listens on 127.0.0.1, do not expose it without an authenticated reverse proxy.

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.

recipe — fail2ban_setup150+ in catalogue
security4 steps · low risk · idempotentrun
reconsshd present? ufw active? existing jails?✓
actinstall fail2ban · write default jails✓
actenable service · restart sshd (safe)✓
verifytest ban 60s · jails active · sshd alive✓

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

Deploy on Servor button

Maintain Grafana Loki 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.

Deploy on ServorDark background
Deploy on ServorLight background
[![Deploy on Servor](https://servor.app/badges/deploy-on-servor.svg)](https://servor.app/deploy/install-loki)

SEC.06

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.