# Migrate DigitalOcean Droplet App: Django

## Summary
Move Django compute from DigitalOcean Droplet 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**: Collect the process environment from the droplet (systemd unit, PM2 or supervisor config) into an env file kept out of the repository. Not migrated automatically: Cron jobs, local upload directories, and firewall rules are not migrated; move uploads to a bucket and data to a managed database.  
**Cutover**: Add the custom domain with `ample domain add`, update DNS from the droplet IP, keep the droplet until verified, then power it off.  
**Rollback**: keep the source untouched until you confirm; nothing at the source is changed or deleted by this guide.

## Prerequisites
- Authorized access to the DigitalOcean Droplet 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

## Workflow Steps
1. **Inventory the source**  
   List what DigitalOcean Droplet app provides beyond the component you are moving. Out of scope here: Cron jobs, local upload directories, and firewall rules are not migrated; move uploads to a bucket and data to a managed database.
2. **Source step 1**  
   Collect the process environment from the droplet (systemd unit, PM2 or supervisor config) into an env file kept out of the repository.
3. **Source step 2**  
   Replace the droplet's process manager and reverse proxy with the repository's start command; Ample provides HTTPS and supervision.
4. **Source step 3**  
   Inventory what else runs on the droplet: databases, cron, local uploads.
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`, update DNS from the droplet IP, keep the droplet until verified, then power it off.
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)**  
  Verified destination basis: Django compute.
  Source Reference: `tests/deploy-canaries/django-patterns`

## Success Checks
- **Destination app responds on its public URL**  
  Kind: `http_get`  
  Path: `/`  
  Expect: `ample canary django patterns`
- **Configuration-secrets check from the destination example**  
  Kind: `http_get`  
  Path: `/p/configuration-secrets`  
  Expect: `see the pattern fixture checks`
- **Relational-records check from the destination example**  
  Kind: `http_get`  
  Path: `/p/relational-records`  
  Expect: `see the pattern fixture checks`
- **Data or object counts and checksums match the source**  
  Kind: `manual`  
  Expect: `operator comparison before cutover`

## Limitations
- Documentation only: nothing is executed automatically and no execution binding is offered.
- The source-side procedure is documented from DigitalOcean Droplet 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: Cron jobs, local upload directories and firewall rules are not migrated; move uploads to a bucket and data to a managed database.
- 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 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  
- **Note**: Destination always-on monthly price of the tested sizes; apps auto-pause when idle. Source costs are unknown to Ample.

## 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). The source-side export from DigitalOcean Droplet app is documented from the vendor's standard tooling and was not executed by this catalog's evidence.  
**Observed At**: 2026-09-20T03:31:44Z  
**Implementation Revision**: 03b6402b1b3e19178985f08ea4033804521d85d4-dirty (CLI b75e104)  
**Expires At**: 2027-03-19T03:31:44Z  
**Scope**:  
Checks: `/p/configuration-secrets`, `/p/relational-records`  
Destination Only: true  
Template: python-3.12

## Next Actions
- **[Browse the catalog index](https://api.ample.computer/v1/catalog)**: Browse published recipes by intent, stack, and constraints.
- **[Prepare a side-effect-free deployment plan](https://api.ample.computer/v1/catalog/plan)**: For an authorized project.