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. 01recondistribution, version and package manager (apt or dnf)
2. 02reconPostgres already installed? which major version(s)?
3. 03reconpostgresql services present and their state
4. 04reconport 5432 already taken? by which process?
5. 05recondoes a cluster already exist? never reinitialize it
6. 06reconPGDG repository already configured?
7. 07actAdd the PGDG repositoryverify
8. 08actInstall PostgreSQL ${version}verify
9. 09actInitialize the cluster (RHEL/Fedora only)verify
10. 10actEnable and startverify
11. 11actCheck the 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.

1. 01verifyAdd the PGDG repositoryVerified byls /etc/apt/sources.list.d/pgdg.list /etc/yum.repos.d/pgdg-*.repo 2>/dev/null | head -1
2. 02verifyInstall PostgreSQL ${version}Verified byls /usr/lib/postgresql/${version}/bin/postgres /usr/pgsql-${version}/bin/postgres 2>/dev/null | head -1
3. 03verifyInitialize the cluster (RHEL/Fedora only)Verified bycat /var/lib/postgresql/${version}/main/PG_VERSION /var/lib/pgsql/${version}/data/PG_VERSION 2>/dev/null | head -1
4. 04verifyEnable and startVerified bysystemctl is-active postgresql@${version}-main postgresql-${version} 2>/dev/null | grep -c '^active'
5. 05verifyCheck the connectionVerified bysudo -u postgres psql -tAc 'show listen_addresses'

SEC.03

Guardrails

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

SEC.04

Variables

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

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.

SEC.06

Deploy on Servor button

Maintain PostgreSQL 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

1. 01MySQLMySQL Server, secured, bound to localhost, started and verified.
2. 02MariaDBMariaDB, secured, bound to localhost, started and verified.
3. 03MongoDBMongoDB Community 9.0, local, with authentication enabled and verified.
4. 04RabbitMQRabbitMQ broker (official repository) with management, local and a dedicated admin account.
5. 05MemcachedMemcached in-memory cache, bound to localhost.