# Host order tracking with Next.js: public product media

Deploy a order tracking built with Next.js on Ample using the public media library 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, and a published bucket serves public assets from the CDN host. Verified on Next.js: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly. Not separately tested: your media processing, object layout and cache policy; treat the order tracking-specific behavior as your application code.

## Representative Queries
- Host order tracking with Next.js: public product media
- Where can I host Order tracking built with Next.js?
- I need product-to-object mappings and a tested public media delivery path.

## Resource Requirements
- primitive:compute
- primitive:postgres
- primitive:s3-compatible-object-storage
- primitive:cdn

## Infrastructure Requirements
### 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.

### 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.

### S3-Compatible Object Storage
- **Status**: verified
- **Summary**: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

### CDN
- **Status**: verified
- **Summary**: The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

## 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 public media library: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly. 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. Publish only the bucket that serves public assets and reference its CDN URL.
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=... --env CDN_PUBLIC_URL=...`
5. **Verify**: Fetch the live URL and the pattern self-test route(s) (`/p/public-media-library`) 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
- Public-media-library self-test

## 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.

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

## Next Actions
- **Browse the catalog index**: `GET /v1/catalog`
- **Search published recipes**: `POST /v1/catalog/search`
- **Prepare deployment plan**: `POST /v1/catalog/plan`
- **Read existing authentication setup**: `GET /mcp/setup`
- **Browse Order tracking**: `GET /v1/catalog/nodes/workload%3Aorder-tracking`
- **Browse Next.js**: `GET /v1/catalog/nodes/stack%3Aframework-next-js`
- **Browse Public media library**: `GET /v1/catalog/nodes/pattern%3Apublic-media-library`
- **Browse Deploy web app**: `GET /v1/catalog/nodes/intent%3Adeploy-web-app`