Host rest api with Fastify: Postgres-backed state · Ample Computer

Host rest api with Fastify: Postgres-backed state

Deploy a Fastify REST API whose durable state lives in a managed PostgreSQL 16 database. With no DATABASE_URL supplied, Ample provisions the database and injects the connection string as an encrypted environment variable; the API stores rows with pg and serves them from a public HTTPS URL.

What it runs on

You need

Exact tested configuration

Steps

  1. Read DATABASE_URL at runtime. Open the connection from the environment inside request handlers or a pool; a local .env is replaced by the managed database in production.

  2. Deploy. Run the existing synchronous deploy once from the project directory and read the result. Exit 0 is live, 1 is failed, 2 needs an answer first (a preflight question). Re-running with no change is a content-addressed no-op.

   $ ample deploy . --name <app-name> --public --format json
  1. 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

✓ root route responds· http get/ → “ample canary fastify postgres api”
✓ database insert and count succeed· 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