Migrate Netlify web app: Django · Ample Computer
Migrate Netlify web app: Django
Move Django compute from Netlify web app to Ample, one component at a time. Destination verified on Ample: the app built, started and answered on its public HTTPS URL with encrypted configuration delivered. Source procedure: Copy environment variables from Site configuration (or netlify env:list) into an env file kept out of the repository. Move separately: Netlify Functions and Edge Functions become routes in the app or a separate Ample service; _redirects/_headers rules, Forms and Identity move into the app or its framework. Cutover: Add the custom domain with ample domain add, set the documented DNS records, keep the Netlify site until verified, then remove the domain from Netlify. Rollback: keep the source untouched until you confirm; nothing at the source is changed or deleted by this guide.
Verified November 6, 2026
What it runs on
Computeverified
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.Postgresverified
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
- Authorized access to the Netlify web app source and its export tooling
- An inventory of every component in scope and out of scope
- A validated backup or copy before any cutover
- An Ample account token with servers:write, databases:read
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
Inventory the source. List what Netlify web app provides beyond the component you are moving. Plan these separately: Netlify Functions and Edge Functions become routes in the app or a separate Ample service;
_redirects/_headersrules, Forms and Identity move into the app or its framework.Source step 1. Copy environment variables from Site configuration (or
netlify env:list) into an env file kept out of the repository.Source step 2. Translate
netlify.tomlbuild settings (command, publish directory) into the repository's own build script; Ample runs the detected build.Source step 3. List Netlify-only features in use: functions, edge functions, forms, identity, redirects and headers rules.
Deploy on Ample in parallel. pip install into .ample/python from requirements.txt, then waitress serving project.wsgi from run.py reading PORT on the python-3.12 template. Pass the exported variables with --env; keep the source running.
$ ample deploy . --name <app-name> --public --start "python3 run.py" --env-file .env.productionValidate before cutover. Run the app's own checks and, for data, compare counts and checksums; the example checks are the pattern self-tests (/p/configuration-secrets, /p/relational-records).
Cut over. Add the custom domain with
ample domain add, set the documented DNS records, keep the Netlify site until verified, then remove the domain from Netlify.Rollback. Point DNS or configuration back to the source. The source was never modified; deletion is a separate, user-executed step after validation.
How it was checked
✓ destination app responds on its public URL· http get/ → “ample canary django patterns”
✓ configuration-secrets check from the destination example· http get/p/configuration-secrets → “see the pattern fixture checks”
✓ relational-records check from the destination example· http get/p/relational-records → “see the pattern fixture checks”
✓ data or object counts and checksums match the source· manual → “operator comparison before cutover”
Evidence
- November 6, 2026 · canary run
Destination side verified: the Django pattern fixture deployed on Ample (pip install into .ample/python from requirements.txt, then waitress serving project.wsgi from run.py reading PORT on the python-3.12 template) and its checks passed (the app built, started and answered on its public HTTPS URL with encrypted configuration delivered). The source-side export from Netlify web app uses the vendor's standard tooling.
Tested examples
- Django pattern fixture (destination). Verified destination basis: Django compute.
What it doesn’t cover
- A step-by-step guide: each stage is an ordinary
ample deploy,ample databaseorample bucketcommand you run. - The destination side was verified on Ample with the pattern fixture; the source-side steps use Netlify web app's standard tooling.
- Plan separately: Netlify Functions and Edge Functions become routes in the app or a separate Ample service;
_redirects/_headersrules, Forms and Identity move into the app or its framework. - Verified on the python-3.12 template at s-1vcpu-1gb.
- Managed PostgreSQL 16 with pgvector. Back up and restore with pg_dump and pg_restore.