PostgreSQL

Reconnaissance — before touching anything

The run starts read-only. Before a single change, Servor checks the real state of your server — a real machine is rarely clean, and only what is actually there decides what happens next.

• 01Postgres already installed? which version?
• 02service active?
• 03port 5432 already taken?
• 04does a cluster already exist? do not reinitialize it

The steps — each one proves itself

The playbook below guides the run; the model adapts each command to the distribution and state found during reconnaissance. A step only counts as done when its verification passes.

1. 01

   Add the PGDG repository

   Verified by

   ls /etc/apt/sources.list.d/pgdg.list 2>/dev/null && echo ok
2. 02

   Install PostgreSQL ${version}

   Verified by

   psql --version
3. 03

   Enable and start

   Verified by

   systemctl is-active postgresql
4. 04

   Check the connection

   Verified by

   sudo -u postgres psql -tAc 'select 1'

Variables

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

${version}

Major version

How Servor runs this recipe

Servor is zero-knowledge: the platform cannot execute anything on its own. When you launch this recipe, an AI 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 to the agent, which verifies the signature locally before executing.