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?
2. 02reconPostgreSQL already installed?
3. 03actInstall PostgreSQL ${version}verify
4. 04actStart the serviceverify

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 PostgreSQL ${version}Verified bybrew list --formula | grep -c "postgresql@${version}"
2. 02verifyStart the serviceVerified bybrew services list | grep "postgresql@${version}" | grep -c started

SEC.03

Variables

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

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

More database recipes

1. 01PostgreSQLPostgreSQL (major version of your choice), initialized, started and verified.
2. 02MySQLMySQL, secured (mysql_secure_installation), started and verified.
3. 03MariaDBMariaDB, started, enabled and verified.
4. 04MongoDBMongoDB Community, started, enabled and verified.
5. 05RabbitMQRabbitMQ message broker with the management plugin.