Files
nixfiles/docs/sites/colony/shill/containers/colony-psql.md
T
jackos1998 5171a10079
CI / Check, build and cache nixfiles (push) Failing after 59m32s
Update docs / update (push) Failing after 1m12s
nixpkgs: Refresh channels and inputs
Rebase the fork branches and refresh nixpkgs, home-manager, and the
approved ancillary inputs. Update kernel and release metadata, adapt
removed package and Home Assistant options, and keep Determinate Nix
on its tested nixpkgs revision to avoid duplicate Boost patches.

Retire Sharry and its public endpoint because copyparty replaces it.
Document the GitHub mirror gate and require real devshell and system
builds in the upgrade validation workflow.
2026-08-24 00:10:18 +01:00

1.7 KiB

colony-psql

The shared PostgreSQL instance for colony services. Rather than each service running its own database, the containers (and the git VM) connect here over the ctrs network.

Role

  • PostgreSQL 14 with TCP/IP enabled, reachable from the whole colony address space using md5 authentication. The firewall allows 5432.
  • Local peer auth maps postgres, root, netdata and dev to the postgres superuser via the ident map.
  • netdata with the Python PostgreSQL collector.
  • Consumers wait for the database to accept connections with the lib.my.systemdAwaitPostgres helper (e.g. atticd, mastodon-init-db, and middleman's nginx as a DNS bootstrap hack).

Network assignments

See the consolidated network assignments table (this box: colony-psql).

The assignment also has the alt name colony-psql (no -ctr suffix), which is what consumers use as the database hostname.

Consumers

  • objecthedgedoc (and atticd when enabled) over colony-psql:5432
  • toot — Mastodon's database (Mastodon currently disabled)
  • chatterbox — the mautrix bridges (WhatsApp, Messenger, Instagram) via Postgres URIs in their secret env files
  • git VM — Gitea

Notable config files