# Migrate Vercel app: Django

## Summary
Move Django compute from Vercel 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 the Vercel project settings (or `vercel env pull`) into an env file you keep out of the repository. Not migrated automatically: Edge middleware, ISR revalidation, image optimization, cron jobs and Vercel integrations are not migrated and are unverified on Ample. Cutover: Add the custom domain with `ample domain add`, set the documented DNS records, keep the Vercel deployment until traffic is verified, then remove the domain from Vercel. Rollback: keep the source untouched until you confirm; nothing at the source is changed or deleted by this guide.

## Representative Queries
- Migrate Vercel app: Django
- Where can I host Django built with Django?
- I need a component-scoped export/import or reconfiguration procedure for Django, with compatibility checks, verification and rollback.

## Resource Requirements
- primitive:compute
- primitive:postgres

## Infrastructure Requirements
1. **Compute**  
   - Status: verified  
   - Summary: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.  
   - [More Info](/discover/primitive/compute)

2. **Postgres**  
   - Status: verified  
   - Summary: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.  
   - [More Info](/discover/primitive/postgres)

## Migration Steps
1. **Inventory the source**  
   List what Vercel app provides beyond the component you are moving. Out of scope here: Edge middleware, ISR revalidation, image optimization, cron jobs and Vercel integrations are not migrated and are unverified on Ample.

2. **Source step 1**  
   Copy environment variables from the Vercel project settings (or `vercel env pull`) into an env file you keep out of the repository.

3. **Source step 2**  
   Note the framework preset, build command and output directory; Ample detects the same from the repository.

4. **Source step 3**  
   List Vercel-only features in use: edge middleware, ISR revalidation, image optimization, cron jobs, integrations.

5. **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.  
   Command: `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 Vercel deployment until traffic is verified, then remove the domain from Vercel.

8. **Rollback**  
   Point DNS or configuration back to the source. The source was never modified; deletion is a separate, user-executed step after validation.

## Examples
### Django pattern fixture (destination)
- Description: Verified destination basis: Django compute.  
- Source Ref: `tests/deploy-canaries/django-patterns`

## Success Checks
- Destination app responds on its public URL  
- Configuration-secrets check from the destination example  
- Relational-records check from the destination example  
- Data or object counts and checksums match the source

## Limitations
- Documentation only: nothing is executed automatically and no execution binding is offered.
- The source-side procedure is documented from Vercel app's standard tooling and was not executed in this catalog's evidence; the destination side was verified with the pattern fixture.
- No full source-product parity is claimed: Edge middleware, ISR revalidation, image optimization, cron jobs and Vercel integrations are not migrated and are unverified on Ample.
- 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.

## Cost Estimate
- Currency: USD
- Monthly Amount: 10.0
- Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty.

### Components
- **App server**  
  - Size: s-1vcpu-1gb  
  - Quantity: 1.0  
  - Monthly Amount: 5.0
- **Managed PostgreSQL database**  
  - Size: s-1vcpu-1gb  
  - Quantity: 1.0  
  - Monthly Amount: 5.0

## Evidence Summary
- 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).

## Next Actions
- [Browse the catalog index](/v1/catalog)  
- [Search published recipes by intent, stack and constraints](/v1/catalog/search)  
- [Prepare a side-effect-free deployment plan](/v1/catalog/plan)  
- [Read the existing agent authentication setup](/mcp/setup)  
- [Browse Vercel app](/v1/catalog/nodes/migration%3Avercel-app)  
- [Browse Django](/v1/catalog/nodes/stack%3Aframework-django)  
- [Browse Migrate compute](/v1/catalog/nodes/intent%3Amigrate-compute)