infrayantra/postgresops-control-plane repository overview

⁠PostgresOps Control Plane

PostgresOps is an API-first control plane for PostgreSQL fleet operations. This image ships a single production-style container: nginx serves the React console and proxies /api, /docs, /redoc, /openapi.json, and /metrics to FastAPI (Uvicorn) on the same host.

Use it when you want the web UI and REST API together without building Node or Python on your machines—pull, wire catalog Postgres + Redis, and go.

⁠What is inside the image

The image does not bundle a PostgreSQL server for your fleet data. For the recommended local/lab stack, run this image next to Postgres 17 (catalog DB) and Redis. A reference stack is docker-compose.hub.yml in the PostgresOps Control Plane source tree (postgresops-enterprise/docker/), alongside env.hub.example for DOCKERHUB_IMAGE.

⁠Tags

• latest — current stable pointer (pin a version tag for reproducible deploys).
• 0.1.0 (and future x.y.z) — semver tags you can pin in production.

⁠Quick start (Docker Compose)

From a checkout of the project, in postgresops-enterprise/:

cp docker/env.hub.example docker/.env.hub
# DOCKERHUB_IMAGE defaults to infrayantra/postgresops-control-plane:latest
docker compose -f docker/docker-compose.hub.yml --env-file docker/.env.hub up -d --pull always

Then open http://localhost:8080⁠ (UI + API) and http://localhost:8080/docs⁠ (Swagger).

⁠Pull only

docker pull infrayantra/postgresops-control-plane:latest

You still need Postgres and Redis reachable from the container, plus env vars (see below). Raw docker run is possible but Compose is the supported path for a full stack.

⁠Required environment (typical)

Optional: POSTGRESOPS_ENV, POSTGRESOPS_BUILD_ID, POSTGRESOPS_LOG_JSON, OpenTelemetry endpoints—see project examples/env.example.

⁠Ports

• Container listens on port 80 (HTTP). Example Compose maps 8080:80 on the host.

⁠Security and scope

• Treat latest as a moving target; use semver tags when you need repeatable rollouts.
• Default Compose examples often use lab passwords; change credentials, network exposure, and TLS before production.
• This is a control plane image: it manages metadata and APIs—it is not a replacement for hardened database images or network policies.

⁠License and support

Software license and support channels follow the upstream project that publishes this image. For build recipes and runbooks, use the repository that contains docker/Dockerfile.unified.

Maintainer: infrayantra⁠ on Docker Hub.