The compose file let the postgres image create TREK's role as the
superuser, so a crafted backup restored by TREK could run commands in the
database container. The superuser is now postgres, with a password of its
own, and an init script creates the role trek that owns TREK's database and
nothing more. The Helm values say the same about the role in the URL.
- wiki/Database-Postgres.md: requirements (PostgreSQL 14 to 17, an empty
database of its own, a role that is not a superuser, ICU), configuration
and SSL, first boot, upgrades and the .pgdump copy, backups and restore,
limitations (no SQLite to Postgres move yet, one replica), notes for
Supabase, and the manual checklist still to run against it.
- docker-compose.postgres.yml: TREK beside a postgres:17 service.
- Helm: database.url (written into the chart's Secret) or
database.existingSecret supplies TREK_DB_URL; replicas stay at one, now
for the state TREK keeps in memory.
- Environment variables, backups, updating, troubleshooting, the Docker
Compose and Helm install pages, the sidebar and the README point at it.