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.
- 01reconHomebrew present? absolute path, prefix owner (brew refuses root: go through sudo -u <owner>), architecture
- 02reconPostgreSQL already installed? which versions and data folders
- 03reconport 5432 free?
- 04reconservice already registered (system or user)? do not duplicate it
- 05actInstall PostgreSQL ${version}verify
- 06actStart the serviceverify
- 07actCheck the local connectionverify
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 PostgreSQL ${version}Verified by
b=$(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/opt/postgresql@${version}/bin/postgres" --version - 02verifyStart the serviceVerified by
launchctl print system/homebrew.mxcl.postgresql@${version} | grep -m1 "state =" - 03verifyCheck the local connectionVerified by
b=$(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/opt/postgresql@${version}/bin/pg_isready" -h 127.0.0.1 -p 5432
SEC.03
Guardrails
Non-negotiable instructions the run must respect, whatever it finds on the server.
If Homebrew is missing, stop and suggest the install-homebrew recipe. Never reinitialize an existing cluster (no initdb on a non-empty data folder). Keep listen_addresses = localhost and trust auth strictly local.
SEC.04
Variables
What you choose before launching — the recipe fills in the rest.
| Name | Meaning |
|---|---|
| ${version} | Major version |
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 PostgreSQL (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.07
More database recipes
- 01PostgreSQLPostgreSQL (major version of your choice) from the official PGDG repository, initialized and verified.
- 02MySQLMySQL Server, secured, bound to localhost, started and verified.
- 03MariaDBMariaDB, secured, bound to localhost, started and verified.
- 04MongoDBMongoDB Community 9.0, local, with authentication enabled and verified.
- 05RabbitMQRabbitMQ broker (official repository) with management, local and a dedicated admin account.
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.