# Configure build and start for Django

Configure build and start for a Django app on Ample. Serve project.wsgi with waitress from run.py reading PORT; pass --start "python3 run.py". Ample detects the runtime, installs dependencies, runs the build when present and starts the app on the python-3.12 template behind a public HTTPS URL.

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

## You need

- A requirements.txt (or pyproject) and a start command that reads PORT and binds 0.0.0.0
- An Ample account token with servers:write

## 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.  **Make the start command bind correctly.** Serve project.wsgi with waitress from run.py reading PORT; pass --start "python3 run.py".

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.

```sh
    $ 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.

```sh
    $ ample logs <deployment_id> --kind build
    ```

## How it was checked

✓ page or root route responds· http get/ → “ample canary django postgres”

## 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-postgres canary.** Django 5 project served by waitress with a managed database.

## What it doesn’t cover

- Verified on the python-3.12 template at s-1vcpu-1gb.
- ALLOWED_HOSTS must include the Ample hostname (the fixture uses *).
