Apply database schema changes for Django · Ample Computer

Apply database schema changes for Django

Apply database schema changes for a Django app on Ample with a release command. python3 manage.py migrate runs against the injected DATABASE_URL before the new release goes live, and the release fails instead of activating if the migration fails.

Verified November 6, 2026

What it runs on

You need

Exact tested configuration

install python3 -m pip install --target .ample/python -r requirements.txt
runtime python
sizes - 1vcpu - 1gb
start PYTHONPATH=.ample/python:${PYTHONPATH:-} python3 run.py
template python-3.12

Steps

  1. Write an idempotent migration. Create tables and markers with IF NOT EXISTS or a migration framework so a re-run is safe.

  2. Deploy with the release command. Ample runs the command before activation; a non-zero exit fails the release.

    $ ample deploy . --name <app-name> --public --start "python3 run.py" --release-command "python3 manage.py migrate"
    ```

3. **Verify the marker through the app.** Serve a route (/migrated) that reads something only the migration creates.

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

✓ migration marker is readable · http get /migrated → “migrated=release-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.

## Tested examples

- **Django release-command canary.** python3 manage.py migrate runs before activation against the auto-provisioned managed database.

## 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.
- The release command runs once per release on the app VM; there is no separate migration runner or rollback of a partially applied migration.