hetzbot-postgres

Provision per-service Postgres databases on a Hetzbot host.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/tomspiegl/hetzbot --skill hetzbot-postgres
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hetzbot-postgres
Source: https://github.com/tomspiegl/hetzbot/tree/main/skills/infra/postgres
Command: npx skills add https://github.com/tomspiegl/hetzbot --skill hetzbot-postgres

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to run a shared Postgres instance on a Hetzbot host, provisioning per-service databases and credentials automatically, while providing rotation, backups, and operational hooks.

Core Features & Use Cases

  • Per-service databases and roles created on demand, with per-service .env files containing connection strings.
  • Docker-Compose-based Postgres 16 stack bound to localhost with non-root execution and secure health checks.
  • Automation for provisioning, rotating passwords, and backing up databases, integrated into the fleet deploy workflow.

Quick Start

Provision a new per-service database by running install.sh <service> on the host where Postgres is deployed.

Frequently Asked Questions about hetzbot-postgres

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I provision a per-service Postgres database on a shared host?

To provision a per-service Postgres database, run the install.sh script with the target service name on the host. This automatically creates the database, sets up roles, and generates a .env file containing the connection string.

What is the best way to automate password rotation for multiple Postgres databases?

Automating password rotation for multiple Postgres databases is handled through built-in scripts that update credentials across per-service roles. This ensures secure, non-root credential management without manual intervention.

Does this Postgres provisioning approach support Docker Compose?

Yes, this Postgres provisioning approach supports Docker Compose by deploying a Postgres 16 stack. The setup binds to localhost, executes as a non-root user, and includes secure health checks.

How do database backups work for shared Postgres instances on a fleet host?

Database backups for shared Postgres instances are executed through provided automation scripts integrated into the fleet deploy workflow. This allows you to back up multiple per-service databases running on the same host.

Can I run multiple services with separate databases on a single Postgres instance?

Yes, you can run multiple services with separate databases on a single Postgres instance. The system provisions per-service databases and roles on demand, generating individual .env files with unique connection strings for each service.

When do I need a shared Postgres instance instead of isolated containers?

You need a shared Postgres instance when managing multiple services on the same host that require automated credential rotation and centralized backups. This approach reduces overhead while maintaining per-service database isolation.