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. 02reconGrafana already installed? version?
  3. 03reconservice active? existing config and database to preserve
  4. 04reconport 3000 free? otherwise who holds it
  5. 05reconreverse proxy present (only useful if a domain is provided)
  6. 06actAdd the Grafana repositoryverify
  7. 07actInstall Grafanaverify
  8. 08actListen on 127.0.0.1verify
  9. 09actEnable and startverify
  10. 10actRandom admin password (fresh install)verify
  11. 11actTLS 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. 01Add the Grafana repositoryVerified byapt-cache policy grafana 2>/dev/null | grep -c Candidate || dnf info grafana -q | grep -c Version
  2. 02Install GrafanaVerified by(dpkg -s grafana 2>/dev/null || rpm -qi grafana) | grep -m1 -i "^version"
  3. 03Listen on 127.0.0.1Verified bygrep -E '^http_addr' /etc/grafana/grafana.ini
  4. 04Enable and startVerified bycurl -s -o /dev/null -w '%{http_code}' http://127.0.0.1:3000/api/health
  5. 05Random admin password (fresh install)Verified bycurl -s -o /dev/null -w '%{http_code}' -u "$(cat /root/grafana-admin.txt)" http://127.0.0.1:3000/api/user
  6. 06TLS reverse proxy (only if a domain is provided)Verified bycurl -s -o /dev/null -w '%{http_code}' https://${domain}/api/health

SEC.03

Guardrails

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

Never reset the admin password of an existing Grafana. Do not touch /var/lib/grafana/grafana.db. Grafana stays on 127.0.0.1 unless behind a TLS reverse proxy. Say where /root/grafana-admin.txt is.

SEC.04

Variables

What you choose before launching — the recipe fills in the rest.

NameMeaning
${domain}Domain (optional)

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.

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

Deploy on Servor button

Maintain Grafana 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-grafana)

SEC.07

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.