# Apply database schema changes for Starlette

Schema changes for a Starlette app on Ample. Verified on Starlette: a --release-command migration ran before activation and its marker was readable by the live app (migrated=release-ok). Build and start: pip install into .ample/python from requirements.txt, then uvicorn from run.py reading PORT on the python-3.12 template.

## 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

- A Starlette project (pip install into .ample/python from requirements.txt, then uvicorn from run.py reading PORT on the python-3.12 template)
- A PostgreSQL driver reading DATABASE\_URL at runtime
- An Ample account token with servers:write, databases:read

## Exact tested configuration

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

runtimepython

sizes-1vcpu-1gb

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

templatepython-3.12

## Steps

1. **Build and start.** pip install into .ample/python from requirements.txt, then uvicorn from run.py reading PORT on the python-3.12 template; the server must bind 0.0.0.0 on PORT.

2. **Run migrations as the release command.** Ample runs the command before activation and fails the release if it exits non-zero; keep migrations idempotent.
   
   ```
   $ ample deploy . --name <app-name> --public --start "python3 run.py" --release-command "python3 migrate.py"
   ```

3. **Verify.** Fetch the live URL and /p/migrated on the example; on failure read the build and runtime logs.
   
   ```
   $ ample logs <deployment_id> --kind build
   ```

## How it was checked

✓ app responds on its public URL· http get/ → “ample canary starlette patterns”  
✓ migrated check from the example· http get/p/migrated → “see the pattern fixture checks”

## Evidence

1. November 6, 2026 · canary run  
   Starlette pattern fixture deployed on Ample (pip install into .ample/python from requirements.txt, then uvicorn from run.py reading PORT on the python-3.12 template); for this guide: a --release-command migration ran before activation and its marker was readable by the live app (migrated=release-ok).

## Tested examples

- **Starlette pattern fixture.** Verified schema changes on Starlette.

## What it doesn’t cover

- Verified on the python-3.12 template at s-1vcpu-1gb.
- Managed PostgreSQL 16 with pgvector.
