page:recipes:subscription content:next js:inventory imports

Host subscription content with Next.js: inventory imports

Summary

Deploy a subscription content 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 subscription content-specific behavior as your application code.

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 <app-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

Input Schema

Required

• env: Encrypted environment variables (bucket credentials, secrets)
• name: App name
• path: Project directory or ample.toml service

Optional

• release_command: Migration command run before activation

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 subscription content itself is application code and was not separately tested; the pattern checks are what was verified.
• Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.

Cost Estimate

• Monthly Amount: $10.00 (USD)
  Based on size prices from pricing.toml at build revision. Components include:
  • App server (s-1vcpu-1gb): $5.00
  • Managed PostgreSQL database (s-1vcpu-1gb): $5.00

Success Checks

• App responds on its public URL.
• Bulk-import-staging self-test.

Examples

• Next.js pattern fixture: Multi-pattern Next.js app whose bulk import staging module was checked live; the module is under tests/deploy-canaries/_pattern-modules.