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. 02reconversion (server_version_num), data_directory, config_file and hba_file of the running cluster
3. 03recontimescaledb already preloaded?
4. 04reconextension already enabled in the database? does the database exist?
5. 05reconTimescale / PGDG repositories present?
6. 06actAdd the Timescale repositoryverify
7. 07actInstall the packageverify
8. 08actConfigure postgresql.confverify
9. 09actRestart PostgreSQL (brief interruption)destructiveverify
10. 10actEnable the extensionverify

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 Timescale repositoryVerified byls /etc/apt/sources.list.d/timescaledb.list /etc/yum.repos.d/timescale_timescaledb.repo 2>/dev/null | head -1
2. 02verifyInstall the packageVerified byls /usr/lib/postgresql/*/lib/timescaledb.so /usr/pgsql-*/lib/timescaledb.so 2>/dev/null | head -1
3. 03verifyConfigure postgresql.confVerified bygrep -E '^shared_preload_libraries' <config_file>
4. 04verifyRestart PostgreSQL (brief interruption)Verified bysudo -u postgres psql -tAc 'select 1'
5. 05verifyEnable the extensionVerified bysudo -u postgres psql -d '${database}' -tAc "select extname from pg_extension where extname='timescaledb'"

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 TimescaleDB 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. 01PostgreSQLPostgreSQL (major version of your choice) from the official PGDG repository, initialized and verified.
2. 02MySQLMySQL Server, secured, bound to localhost, started and verified.
3. 03MariaDBMariaDB, secured, bound to localhost, started and verified.
4. 04MongoDBMongoDB Community 9.0, local, with authentication enabled and verified.
5. 05RabbitMQRabbitMQ broker (official repository) with management, local and a dedicated admin account.