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. 02reconGlances already present (package or /opt/glances venv)? version?
  3. 03reconweb service already active?
  4. 04reconport 61208 free?
  5. 05reconPython 3.9+ with the venv module?
  6. 06actInstall Python venvverify
  7. 07actInstall Glances with web modeverify
  8. 08actWeb service on 127.0.0.1:61208verify
  9. 09actThe UI respondsverify

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 Python venvVerified bypython3 -c "import venv" && echo ok
  2. 02Install Glances with web modeVerified by/opt/glances/bin/glances --version
  3. 03Web service on 127.0.0.1:61208Verified bysystemctl is-active glances
  4. 04The UI respondsVerified bycurl -s -o /dev/null -w '%{http_code}' http://127.0.0.1:61208/

SEC.03

Guardrails

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

Web mode has no auth by default: it listens on 127.0.0.1, never expose it publicly without a protected reverse proxy. Do not pip install into the system Python (venv only).

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 Glances 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-glances)

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.