Skip to content

PostGIS Service documentation

PostGIS Service is the AcuGIS federation component for registering PostgreSQL servers, provisioning and inspecting PostGIS databases, managing PostgreSQL roles and network access, running backup/restore/vector-import jobs, and providing administrator terminals.

The service exposes a browser UI and JSON API from one Go process. It requires a metadata PostgreSQL database and a Central authentication database; managed PostgreSQL servers may be local or remote. There is no health endpoint or metrics endpoint in the current source.

Documentation

Capabilities

Area Implemented behavior
Connections Register, update, delete, test, inspect databases and PostGIS
Databases Create, delete, same-server clone, inspect schemas/tables/spatial metadata
Data movement Custom-format backup/restore and vector upload/import
PostgreSQL access Login roles, group roles, memberships, database privilege bundles
Network access Curated pg_hba.conf rules and PostgreSQL reload
Settings Read/update a curated pg_settings allowlist through ALTER SYSTEM
Jobs Persistent asynchronous queue polled by an in-process worker
Terminals Administrator-only psql, restricted server command, and journal log WebSockets

Important boundaries

  • Central owns users, sessions, groups, resources, and service permissions; this service reads those tables and does not provide Central administration endpoints.
  • The source contains no container image, Kubernetes manifest, database down-migration, API version prefix, rate limiting, CORS middleware, request tracing, metrics, or graceful HTTP shutdown.
  • Stored PostgreSQL administrator passwords are AES-256-GCM encrypted only when POSTGIS_SECRETS_KEY is configured. Without it, new values are stored with a plain: prefix.
  • The sibling ACUGIS CLI declares acugis db commands, but all six currently call not_implemented(); see CLI status.