Migrate DigitalOcean Droplet app: Next.js

Move Next.js 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.

Migration Steps

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
   next build then next start -H 0.0.0.0 -p $PORT on the node-22 template. Pass the exported variables with --env; keep the source running.
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.

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.
• Cron jobs, local upload directories and firewall rules are not migrated; move uploads to a bucket and data to a managed database.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Components:
  • App server: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: 5.0
  • Managed PostgreSQL database: 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 Next.js pattern fixture deployed on Ample and its checks passed.

Next Actions

• Browse the catalog index
• Search published recipes by intent, stack and constraints
• Prepare a side-effect-free deployment plan for an authorized project
• Read the existing agent authentication setup
• Browse DigitalOcean Droplet app
• Browse Next.js
• Browse Migrate compute