Connect Postgres for Fastify · Ample Computer

Connect Postgres for Fastify

Connect a Fastify app to PostgreSQL on Ample. Read DATABASE_URL at runtime with pg: when you supply one with --env it is delivered encrypted and takes precedence; when you supply none and the app needs PostgreSQL, Ample auto-provisions a managed PostgreSQL 16 database and injects its connection string.

What it runs on

You need

Exact tested configuration

  1. build npm run build --if-present
  2. install npm install
  3. runtime node
  4. sizes - 1vcpu-1gb
  5. start npm run start
  6. template node-22

Steps

  1. Read the URL at runtime. Open connections from the DATABASE_URL environment variable inside the app; never commit credentials and never connect at build time.

  2. Choose the source of the database. Pass --env DATABASE_URL=... for an existing database, or omit it to let Ample provision a managed one on first deploy and reuse it on redeploys.

   $ ample deploy . --name <app-name> --public
  1. Test the connection through the app. Expose a route (/items) that runs a trivial query and returns postgres=ok.

  2. Verify. Fetch the live URL and run the success checks below. On failure read the build log, then the runtime log, fix the cause and deploy again; do not blind-retry.

   $ ample logs <deployment_id> --kind build

How it was checked

✓ database route reports a live connection · http get/items → “postgres=ok”

Evidence

  1. November 5, 2026 · canary run Fastify REST API using pg with no DATABASE_URL supplied: Ample auto-provisioned a managed PostgreSQL 16 database and /items reported postgres=ok after a real insert and count.

  2. November 6, 2026 · canary run Node app needing PostgreSQL with no DATABASE_URL: a managed database was auto-provisioned and /db reported postgres=ok.

Tested examples

What it doesn’t cover