digitalocean-labs/do-app-platform-skills

postgres

Configure DigitalOcean Managed Postgres with bindable variables or schema isolation. Use when setting up databases, creating users, managing permissions, configuring multi-tenant schemas, or troubleshooting database connectivity on App Platform.

First seen Jun 8, 2026

Installation

$ npx skills add digitalocean-labs/do-app-platform-skills --skill postgres

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from digitalocean-labs/do-app-platform-skills · top by installs.

npx skills add digitalocean-labs/do-app-platform-skills

Browse all from digitalocean-labs/do-app-platform-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 36
License LICENSE
Default branch main
Open issues 1
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.0

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 4,482 B
  • docs SUMMARY.md 261 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 41 installs

SKILL.md

Postgres Skill

Configure DigitalOcean Managed Postgres databases with proper security isolation and production-ready defaults.

Quick Decision

Need multiple isolated schemas in one database?
├── YES → Path B (Schema Isolation)
└── NO  → Path A (Bindable Variables) ✅ RECOMMENDED

Path A: Bindable Variables (Recommended)

Use when: Single app per database, standard CRUD applications.

Quick Start

# 1. Create cluster + user via doctl (DO stores password internally)
doctl databases create my-app-db --engine pg --region nyc3 --size db-s-1vcpu-2gb
CLUSTER_ID=$(doctl databases list --format ID,Name --no-header | grep my-app-db | awk '{print $1}')
doctl databases db create $CLUSTER_ID myappdb
doctl databases user create $CLUSTER_ID myappuser

# 2. Grant permissions (REQUIRED - users have no access by default!)
# Run: scripts/grant_permissions.sql as doadmin

# 3. Reference in app spec
# .do/app.yaml
databases:
  - name: db
    engine: PG
    production: true
    cluster_name: my-app-db
    db_name: myappdb
    db_user: myappuser

services:
  - name: api
    envs:
      - key: DATABASE_URL
        scope: RUN_TIME
        value: ${db.DATABASE_URL}

Full guide: See [path-a-bindable-vars.md](reference/path-a-bindable-vars.md)


Path B: Schema Isolation

Use when: Multi-tenant SaaS, multiple apps sharing one cluster, schema-level isolation needed.

Quick Start

# Hands-free setup (requires gh CLI)
./scripts/secure_setup.sh \
  --admin-url "$ADMIN_URL" \
  --app-name myapp \
  --schema myapp \
  --repo owner/repo

Password flows directly to GitHub Secrets — never displayed.

Full guide: See [path-b-schema-isolation.md](reference/path-b-schema-isolation.md)


Available Bindable Variables

Variable Example
${db.DATABASE_URL} postgresql://user:pass@host:25060/db?sslmode=require
${db.HOSTNAME} my-db-do-user-123.db.ondigitalocean.com
${db.PORT} 25060
${db.USERNAME} myappuser
${db.PASSWORD} (auto-populated)
${db.DATABASE} myappdb
${db.CA_CERT} (certificate content)

Scripts

Script Purpose
scripts/secure_setup.sh Hands-free Path B setup with GitHub Secrets
scripts/createschemauser.py Create isolated schema + user
scripts/listschemasusers.py Audit existing schemas/users
scripts/generateconnectionstring.py Build connection strings

Reference Files

  • [path-a-bindable-vars.md](reference/path-a-bindable-vars.md) — Full Path A workflow, connection pools, multi-app setup
  • [path-b-schema-isolation.md](reference/path-b-schema-isolation.md) — Full Path B workflow, multi-tenant patterns
  • [orm-configurations.md](reference/orm-configurations.md) — Prisma, SQLAlchemy, Drizzle, TypeORM configs
  • [database-migrations.md](reference/database-migrations.md) — Alembic, Prisma Migrate, Drizzle Migrate
  • [doctl-reference.md](reference/doctl-reference.md) — All doctl databases commands
  • [troubleshooting.md](reference/troubleshooting.md) — Common errors and fixes
  • [bundled-scripts.md](reference/bundled-scripts.md) — Script usage documentation

Common Issues (Quick Fixes)

Error Fix
"permission denied for schema" Run permission SQL as doadmin
"relation does not exist" Check search_path or use schema-qualified names
"too many connections" Create connection pool via doctl
"SSL connection required" Add ?sslmode=require to connection string
Bindable vars not populated Verify production: true and names match exactly

Full troubleshooting: See [troubleshooting.md](reference/troubleshooting.md)


Integration with Other Skills

  • → designer: Add database block to app spec
  • → deployment: GitHub Actions workflow with DATABASE_URL secret
  • → devcontainers: Local Postgres with prod parity
  • → troubleshooting: Debug container for connectivity testing