config/, turn the bundled database off, and start. Do this on a new install:
the bundled database’s data isn’t moved.
Before you begin
- Fonoster downloaded and unpacked, but not started yet, see Install with Docker Compose.
- A Postgres you can reach from this machine, over TLS. Every URL below ends in
?sslmode=require; keep it, or the password and your call data travel in clear. Certificate verification (sslmode=verify-full) isn’t covered here. - Docker Compose v2, as the install page says.
Create the databases
Create three empty databases. The API server creates the tables infonoster and fnidentity
on every start, and Routr does the same in routr:
Point every service at it
Each service takes its database URL from its file inconfig/, with the same credentials in all
four. Replace the bundled URL in each. In config/fonoster.yaml, set the API server’s database
and Identity’s identity.database:
config/fonoster.yaml
database.url in
config/appbridge.yaml and in config/autopilot.yaml:
config/appbridge.yaml
spec.database in config/routr-one.yaml:
config/routr-one.yaml
.env, and carry them over when you
upgrade.
Turn the bundled Postgres off
Thecompose.external-db.yaml overlay that ships with the install keeps the bundled postgres
from starting. Turn it on in .env (add :compose.http.yaml after it if you serve plain HTTP):
.env
compose.external-db.yaml
Start
Start, and wait for every service to be healthy. This is what proves the database is reachable:routr can’t reach its database, it reports unhealthy and the command exits with an error.
Fix the URL in config/routr-one.yaml and start again. A file with a bad key stops its service at
start, and docker compose logs <service> names the key.
See what’s running:
postgres isn’t listed, and routr shows healthy.
Every service runs against your database.
On an external Postgres, the registry tool on
Add providers to the catalog needs your database URL in
FONOSTER_REGISTRY_DATABASE_URL instead of the bundled one.