Administration
Databases
Forge’s internal PostgreSQL and Redis are not the same thing as databases provisioned for hosted workloads.
#Forge internal data services
| Service | Image and port | Purpose |
|---|---|---|
| PostgreSQL | postgres:16-alpine, private :5432 | Durable source of truth, migrations, control-plane records. |
| Redis | redis:7-alpine, private :6379 | Runtime coordination with append-only persistence. |
| PostgreSQL backup | postgres:16-alpine sidecar | Scheduled database dumps to the configured local path and optional S3 settings. |
#Emergency inspection
docker compose -f compose.yml -f compose.production.yml --env-file .env exec postgres psql -U "$POSTGRES_USER" -d "$POSTGRES_DB"
docker compose -f compose.yml -f compose.production.yml --env-file .env exec redis redis-cli ping#Hosted workload databases
The administration surface includes database services and managed database provisioning. The API wires a container provisioner to Beacon and Docker. Supported engine options must be selected in the dashboard and verified against the chosen node; keep their credentials, network exposure, backup policy, and lifecycle separate from Forge’s own PostgreSQL.
An application or game server should receive only its own database host, database, and least-privilege user.
#Backup and restore
The control-plane backup sidecar uses POSTGRES_BACKUP_HOST_DIR by default and can receive S3_BACKUP_* configuration. Workload backup adapters are configured on Beacon with BACKUP_ADAPTER and S3_* variables. Test a restore on an eligible destination before relying on recovery.