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 and version: apt (Debian/Ubuntu) or dnf (RHEL/Fedora/Rocky/Alma)?
- 02reconRedis (or Valkey) already installed? which version?
- 03reconwhich service is active (redis-server on Debian, redis on RHEL, valkey on Fedora/RHEL 10)?
- 04reconwhere is the config? (requirepass/bind already set?)
- 05reconis port 6379 already taken (by which process)?
- 06actInstall Redis (if missing)verify
- 07actEnable and startverify
- 08actEnable requirepass (only if a password is provided)verify
- 09actListen on localhost onlyverify
- 10actRedis 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 Redis (if missing)Verified by
redis-server --version 2>/dev/null || valkey-server --version - 02verifyEnable and startVerified by
systemctl is-active redis-server 2>/dev/null || systemctl is-active redis 2>/dev/null || systemctl is-active valkey - 03verifyEnable requirepass (only if a password is provided)Verified by
redis-cli --no-auth-warning -a '${password}' ping - 04verifyListen on localhost onlyVerified by
ss -tlnH "sport = :6379" | grep -vcE "127\.0\.0\.1|\[::1\]" - 05verifyRedis respondsVerified by
redis-cli ping
SEC.03
Guardrails
Non-negotiable instructions the run must respect, whatever it finds on the server.
Never let Redis listen beyond localhost without a password, and do not open 6379 in the firewall. Redis already active → verify and report, do not reinstall. Never run FLUSHALL/FLUSHDB. Back up the config before any change.
SEC.04
Variables
What you choose before launching — the recipe fills in the rest.
| Name | Meaning |
|---|---|
| ${password} | Password (requirepass) |
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.
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 Redis 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.
Dark background
Light background[](https://servor.app/deploy/install-redis)SEC.07
More cache & queues recipes
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.