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

### Migration Overview

**Source procedure:** Copy environment variables from Site configuration (or `netlify env:list`) into an env file kept out of the repository.

**Not migrated automatically:** Netlify Functions, Edge Functions, Forms, Identity and `_redirects`/`_headers` rules are not migrated; implement redirects in the app or the 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.

### Prerequisites

- 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

### Resource Requirements

- **Compute**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
- **Postgres**: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

### Workflow Steps

1. **Inventory the source**: List what Netlify web app provides beyond the component you are moving. Out of scope here: Netlify Functions, Edge Functions, Forms, Identity and `_redirects`/`_headers` rules are not migrated; implement redirects in the app or the framework.
2. **Source step 1**: Copy environment variables from Site configuration (or `netlify env:list`) into an env file kept out of the repository.
3. **Source step 2**: Translate `netlify.toml` build settings (command, publish directory) into the repository's own build script; Ample runs the detected build.
4. **Source step 3**: List Netlify-only features in use: functions, edge functions, forms, identity, redirects and headers rules.
5. **Deploy on Ample in parallel**: `ample deploy . --name  --public --start "python3 run.py" --env-file .env.production`.
6. **Validate 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).
7. **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.
8. **Rollback**: Point DNS or configuration back to the source. The source was never modified; deletion is a separate, user-executed step after validation.

### Limitations

- Documentation only: nothing is executed automatically and no execution binding is offered.
- The source-side procedure is documented from Netlify web app's standard tooling and was not executed in this catalog's evidence; the destination side was verified with the pattern fixture.
- Verified on the python-3.12 template at s-1vcpu-1gb; region, compliance and request-duration limits are unknown.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures on the managed side are not verified beyond the pattern checks.

### Success Checks

- **Destination app responds on its public URL**: Check the `/` path for response.
- **Configuration-secrets check**: Access to `/p/configuration-secrets` should meet expectations.
- **Relational-records check**: Access to `/p/relational-records` should meet expectations.
- **Data or object counts and checksums match the source**: Manual comparison required before cutover.

### Cost Estimate

- **Monthly Amount**: $10.00
- **Components**:
  - App server `s-1vcpu-1gb`: $5.00
  - Managed PostgreSQL database `s-1vcpu-1gb`: $5.00

### Evidence Summary

Destination side verified: the Django pattern fixture deployed on Ample and its checks passed. The source-side export from Netlify web app is documented from the vendor's standard tooling and was not executed by this catalog's evidence.

### Formats

- HTML: [Migrate Netlify web app: Django](/content/migrate/netlify-web-app/django/index.html)
- Markdown: [Migrate Netlify web app: Django](/content/migrate/netlify-web-app/django.md)
- JSON: [Migrate Netlify web app: Django](https://api.ample.computer/v1/catalog/recipes/page%3Amigrate%3Anetlify-web-app%3Adjango)