dibbla db

Provision managed Postgres databases, connect through the Dibbla proxy, and dump/restore using `pg_dump` custom-format archives.

dibbla db manages Postgres databases on the Dibbla platform. Each database is reachable from your apps via an automatically created secret, and from your laptop via the database proxy at db.dibbla.com:30432 (host derived from DIBBLA_API_URL).

dibbla db list

$dibbla db list
🌱 Retrieving databases...
 
Found 2 database(s):
 
   main
   nextjs_todo_db

# -q prints names only, one per line
$dibbla db list -q | xargs -I{} dibbla db dump {}

dibbla db create

Provision a new database. Names must start with a letter, contain only a–z, 0–9 and _, and be at most 60 characters (^[a-z][a-z0-9_]{0,59}$). Uppercase input is lowercased for you rather than rejected.

When you create a database, a secret is created with it:

The name is always DATABASE_URL_<UPPERCASE_NAME> — lumen_incidents becomes DATABASE_URL_LUMEN_INCIDENTS. There is never a plain DATABASE_URL, whatever the scope, so application code has to read the suffixed variable.

--deployment changes the secret’s scope, not its name: global to the organisation by default, or visible only to one deployment.

$dibbla db create main
🌱 Creating database 'main'...
 
✅ Database 'main' created successfully
  Database: main
  Secret:   DATABASE_URL_MAIN (auto-created)
 
  This is a global secret available to all deployments in your org.
  It will be injected automatically on every deploy.

$dibbla db create todo --deployment my-api
🌱 Creating database 'todo' (scoped to deployment 'my-api')...
 
✅ Database 'todo' created successfully
  Database: todo
  Secret:   DATABASE_URL_TODO (auto-created)
 
  The secret is scoped to deployment 'my-api'.
  It will be injected automatically when that deployment starts.

dibbla db delete

Permanently delete a database. Cannot be undone.

$dibbla db delete main --yes
🗑️ Attempting to delete database 'main'...
 
✅ Database 'main' deleted successfully

dibbla db dump

Download a pg_dump custom-format archive — compatible with pg_restore.

$dibbla db dump main
🌱 Dumping database 'main' to /Users/jane/projects/main.dump...
 
✅ Dump saved to /Users/jane/projects/main.dump
 
$dibbla db dump main --output backup-$(date +%F).dump

# Standard pg_restore against any local Postgres
$pg_restore --no-owner -d local_db main.dump

dibbla db restore

Restore a database from a dump file.

$dibbla db restore main --file backup.dump
🌱 Restoring database 'main' from backup.dump...
 
✅ Database 'main' restored successfully

dibbla db connect

Print a psql-compatible connection string.

The CLI first asks the platform where the proxy is — GET /api/deploy/db/proxy-info, with a five-second timeout. If that call succeeds its answer wins, which means the host, port and TLS mode can change server-side without a CLI release. Only when it fails or times out does the CLI fall back to deriving them from DIBBLA_API_URL:

Override any of it with DIBBLA_DB_HOST, DIBBLA_DB_PORT (default 30432) or DIBBLA_DB_SSLMODE — these win over both the served answer and the fallback. Your current API token is used as the password, which is why the string must never be pasted anywhere it can be read: pass it with command substitution, psql $(dibbla db connect main -q), and never pipe it — psql reads standard input as SQL and would echo your token back inside a syntax error.

$dibbla db connect main
🔗 Connection string for database 'main':
 
  postgres://dibbla:dbb_***@db.dibbla.com:30432/main?sslmode=require
 
Quick connect:
  psql $(dibbla db connect main -q)
 
Or export as an environment variable:
  export DATABASE_URL=$(dibbla db connect main -q)

# -q prints just the connection string, suitable for $()
$psql $(dibbla db connect main -q)

$export DATABASE_URL=$(dibbla db connect main -q)
$npx prisma migrate dev

openssl s_client -connect db.dibbla.com:30432 -starttls postgres

See also

• dibbla secrets — inspect or override the auto-created DATABASE_URL_<NAME>.
• dibbla deploy — deploy an app that consumes the database via its bound secret.