External PostgreSQL
Use your own PostgreSQL instead of the bundled one
The kit bundles PostgreSQL 17 with the pgvector extension. To use your own server:
- PostgreSQL 15 or newer with the
vectorextension available (CREATE EXTENSION vector;must succeed — the knowledge graph depends on it). - Create a database and a user that owns it.
- In
.env, setDATABASE_URLand leaveTESTINGOPS_DB_*empty:
DATABASE_URL=postgres://testingops:secret@db.company.local:5432/testingops?sslmode=require
./install.sh— withDATABASE_URLset the bundled database is not started (docker composeruns without thebundled-dbprofile) and migrations run against your server.
Backups: backup.sh cannot dump an external database from inside the kit; schedule pg_dump -Fc
on your database server and keep it together with the application data backup.
Managed services that work: Amazon RDS / Aurora PostgreSQL, Azure Database for PostgreSQL,
Google Cloud SQL — all offer pgvector. Connection pooling in transaction mode (PgBouncer) is not
supported for the migration step; point DATABASE_URL at the server directly.