# Host digital downloads with Next.js: inventory imports

### Summary
Deploy a digital downloads built with Next.js on Ample using the bulk import staging pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, a managed PostgreSQL 16 database is auto-provisioned and injected as DATABASE_URL, a private S3-compatible bucket holds objects with credentials delivered as encrypted environment variables. Verified on Next.js: a CSV staged as an object, row-level validation with per-row errors recorded, and a restart-safe import keyed by import id (imported=2 rejected=1 restart=ok). Not separately tested: your import format, mapping and conflict rules; treat the digital downloads-specific behavior as your application code.

### Framework
Next.js

### Workload
Digital downloads

### Release Status
Published

### Support Status
Verified

### Execution Status
Ready

### Prerequisites
- A Next.js project that builds and starts with the documented commands (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template)
- A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
- A bucket from `ample bucket create` with its credentials passed as encrypted S3_* environment variables
- An Ample account token with servers:write, databases:read, buckets:read

### Tested Configuration
- Template: node-22
- Runtime: node
- Size: s-1vcpu-1gb
- Install: npm install
- Build: npm run build --if-present
- Start: npm run start

### Workflow Steps
1. **Build and start**: next build then next start -H 0.0.0.0 -p $PORT on the node-22 template. The server must bind 0.0.0.0 on PORT.
2. **Implement the pattern on PostgreSQL**: The fixture's module implements bulk import staging: a CSV staged as an object, row-level validation with per-row errors recorded, and a restart-safe import keyed by import id (imported=2 rejected=1 restart=ok). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.
3. **Wire object storage**: Create the bucket(s), then pass endpoint, region, bucket and keys as --env values. Use path-style addressing. Keep private data in an unpublished bucket.
4. **Deploy**: Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 blocked). Re-running with no change is a no-op.
   Command: ample deploy . --name  --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...
5. **Verify**: Fetch the live URL and the pattern self-test route(s) (/p/bulk-import-staging) from the example; then run your own checks. On failure read `ample logs  --kind build` then `--kind runtime`.
   Command: ample logs  --kind build

### Success Checks
- App responds on its public URL
   Kind: http_get
   Path: / 
   Expect: ample canary next js patterns
- Bulk-import-staging self-test
   Kind: http_get
   Path: /p/bulk-import-staging
   Expect: imported=2 rejected=1 restart=ok

### Limitations
- Verified on the node-22 template at s-1vcpu-1gb with the example fixture; other sizes, templates and Next.js major versions are not verified.
- The digital downloads itself (your import format, mapping and conflict rules) is application code and was not separately tested; the pattern checks are what was verified.
- Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.

### Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Authoritative**: true
- **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
- **Note**: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

### Evidence Summary
- **Canary Run** 
  - Summary: Next.js pattern fixture deployed on Ample (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template); checks passed for bulk-import-staging and configuration-secrets. 
  - Observed At: 2026-09-21T02:34:39Z
  - Implementation Revision: 1d28ae0-dirty (CLI 0.1.21)
  - Expires At: 2027-03-20T02:34:39Z

### 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 Digital downloads](#)
- [Browse Next.js](#) 
- [Browse Bulk import staging](#)
- [Browse Deploy web app](#)

---
