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

Host rest api with Flask: Postgres-backed state

Deploy a Flask 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 psycopg and serves them from a public HTTPS URL.

What it runs on

You need

Exact tested configuration

installpython3 -m pip install --target .ample/python -r requirements.txt

runtimepython

sizes-1vcpu-1gb

startPYTHONPATH=.ample/python:${PYTHONPATH:-} python3 app.py

templatepython-3.12

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 --start "python3 run.py"
    
  3. 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 flask postgres app”
✓database insert and count succeed· http get/items → “postgres=ok”

Evidence

  1. November 6, 2026 · canary run
    Flask app (waitress) using psycopg with an auto-provisioned managed PostgreSQL database: /items reported postgres=ok and /config confirmed the encrypted secret.

  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