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.
- 01recondistro (apt or dnf) and architecture (amd64/arm64)
- 02reconGlances already present (package or /opt/glances venv)? version?
- 03reconweb service already active?
- 04reconport 61208 free?
- 05reconPython 3.9+ with the venv module?
- 06actInstall Python venvverify
- 07actInstall Glances with web modeverify
- 08actWeb service on 127.0.0.1:61208verify
- 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.
- 01verifyInstall Python venvVerified by
python3 -c "import venv" && echo ok - 02verifyInstall Glances with web modeVerified by
/opt/glances/bin/glances --version - 03verifyWeb service on 127.0.0.1:61208Verified by
systemctl is-active glances - 04verifyThe UI respondsVerified by
curl -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.
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.
SEC.06
More observability recipes
- 01node_exporterPrometheus system metrics exporter, as a systemd service.
- 02NetdataNetdata real-time monitoring (stable channel), local dashboard on :19999.
- 03PrometheusPrometheus (metrics collection), as a local systemd service on :9090.
- 04GrafanaGrafana OSS (official repo), local on :3000, admin with a random password.
- 05Grafana LokiLoki 3.7 log aggregation via Docker, local on :3100.
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.