# Connect Postgres for Django

Connect a Django app to PostgreSQL on Ample. Read `DATABASE_URL` at runtime with `dj-database-url` with `psycopg`: 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.

**Verified** November 6, 2026

## What it runs on

- [Computeverified](/content/discover/primitive/compute/index.html)
    Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

- [Postgresverified](/content/discover/primitive/postgres/index.html)
    Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no `DATABASE_URL` is supplied.

## You need

- `dj-database-url` with `psycopg` reading the `DATABASE_URL` environment variable at runtime
- Either a production `DATABASE_URL` to pass with --env, or nothing (auto-provision)
- An Ample account token with `servers:write` and `databases:read`

## Exact tested configuration

```bash
install python3 -m pip install --target .ample/python -r requirements.txt
```

runtime

```bash
sizes-1vcpu-1gb
start PYTHONPATH=.ample/python:${PYTHONPATH:-} python3 run.py
template python-3.12
```

## 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.
   
   ```bash
   $ ample deploy . --name <app-name> --public --start "python3 run.py"
   ```

3. **Test the connection through the app.** Expose a route (`/db`) that runs a trivial query and returns `postgres=ok`.

4. **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.
   
   ```bash
   $ ample logs <deployment_id> --kind build
   ```

## How it was checked

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

## Evidence

1. November 6, 2026 · canary run
   Django 5 project with `dj-database-url` and `psycopg`: the managed PostgreSQL database was auto-provisioned, `python3 manage.py migrate` ran as the release command, and `/db` and `/migrated` reported `postgres=ok` and the migrated marker.

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

- **Django + PostgreSQL canary.** Auto-provisioned managed database with a real query.

## What it doesn’t cover

- Verified on the `python-3.12` template at `s-1vcpu-1gb`.
- Managed PostgreSQL 16 with pgvector.
- Apps and their managed databases are placed together, in the same region.
