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.
- 01recondoes a PostgreSQL already exist? which version, service and folder
- 02reconport 5432 free?
- 03reconavailable package managers: winget (real path, often off PATH under SYSTEM), choco, and the account running commands
- 04reconfree disk space on C: (≥ 2 GB recommended)
- 05actGenerate the superuser passwordverify
- 06actInstall PostgreSQL ${version}verify
- 07actCheck the local connectionverify
- 08actCheck network exposureverify
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.
- 01verifyGenerate the superuser passwordVerified by
Test-Path "$env:ProgramData\Servor\secrets\postgresql-${version}-postgres.txt" - 02verifyInstall PostgreSQL ${version}Verified by
(Get-Service "postgresql-x64-${version}").Status - 03verifyCheck the local connectionVerified by
& "$env:ProgramFiles\PostgreSQL\${version}\bin\pg_isready.exe" -h 127.0.0.1 -p 5432 - 04verifyCheck network exposureVerified by
(Get-NetFirewallPortFilter | Where-Object LocalPort -eq 5432 | Get-NetFirewallRule | Where-Object { $_.Enabled -eq "True" -and $_.Action -eq "Allow" } | Measure-Object).Count
SEC.03
Guardrails
Non-negotiable instructions the run must respect, whatever it finds on the server.
Never overwrite an existing cluster or its data folder. The superuser password stays in the secrets file, never displayed or logged. Do not open port 5432 in the firewall and do not widen pg_hba.conf.
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 (Windows) 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.