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. 01reconHomebrew present? absolute path, prefix owner (brew refuses root: go through sudo -u <owner>), architecture
2. 02reconRedis already installed?
3. 03reconexisting config: bind, port, protected-mode, password
4. 04reconport 6379 free?
5. 05reconservice already registered (system or user)? do not duplicate it
6. 06actInstall Redisverify
7. 07actStart the serviceverify
8. 08actCheck the responseverify

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. 01verifyInstall RedisVerified byb=$(ls /opt/homebrew/bin/brew /usr/local/bin/brew 2>/dev/null | head -1); u=$(stat -L -f %Su "$b"); p=$(dirname "$(dirname "$b")"); "$p/bin/redis-server" --version
2. 02verifyStart the serviceVerified bylaunchctl print system/homebrew.mxcl.redis | grep -m1 "state ="
3. 03verifyCheck the responseVerified byb=$(ls /opt/homebrew/bin/brew /usr/local/bin/brew 2>/dev/null | head -1); u=$(stat -L -f %Su "$b"); p=$(dirname "$(dirname "$b")"); "$p/bin/redis-cli" -h 127.0.0.1 ping

SEC.03

Guardrails

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

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.

SEC.05

Deploy on Servor button

Maintain Redis (macOS) 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 database recipes

1. 01PostgreSQLPostgreSQL (major version of your choice) from the official PGDG repository, initialized and verified.
2. 02MySQLMySQL Server, secured, bound to localhost, started and verified.
3. 03MariaDBMariaDB, secured, bound to localhost, started and verified.
4. 04MongoDBMongoDB Community 9.0, local, with authentication enabled and verified.
5. 05RabbitMQRabbitMQ broker (official repository) with management, local and a dedicated admin account.