Configure build and start for Flask · Ample Computer
Configure build and start for Flask
Configure build and start for a Flask app on Ample. Serve the WSGI app with a production server such as waitress from app.py reading PORT; pass --start "python3 app.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
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
install python3 -m pip install --target .ample/python -r requirements.txt
runtime python
sizes - 1vcpu-1gb
start PYTHONPATH=.ample/python:${PYTHONPATH:-} python3 app.py
template python-3.12
Steps
Make the start command bind correctly. Serve the WSGI app with a production server such as waitress from app.py reading PORT; pass --start "python3 app.py".
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.
$ 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 flask basic”
## Evidence
1. November 5, 2026 · canary run
Flask app served by waitress on python-3.12 and rendered the expected response.
## Tested examples
- **flask-basic canary.** Flask app served by waitress.
## What it doesn’t cover
- Verified on the python-3.12 template at s-1vcpu-1gb.
- Serve Flask with waitress (tested); the development server is for local use.