Apply database schema changes for Flask · Ample Computer

Apply database schema changes for Flask

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

What it runs on

You need

Exact tested configuration

python3 -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. 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 migrate.py"
  1. Verify the marker through the app. Serve a route (/migrated) that reads something only the migration creates.

  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

✓ migration marker is readable· http get/migrated → “migrated=release-ok”

Evidence

  1. November 6, 2026 · canary run
    The same Flask app deployed with --release-command python3 migrate.py; /migrated reported the migration marker.

Tested examples

What it doesn’t cover