## Host marketplace with Next.js: public product media

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

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

### 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 and a second, published bucket for public assets (`CDN_*`)
- An Ample account token with `servers:write`, `databases:read`, `buckets:read`

### Infrastructure Requirements
1. **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.
2. **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.
3. **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.
4. **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**  
   - Command: `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 <your-app-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
1. **App responds on its public URL**  
   - Kind: `http_get`  
   - Path: `/`  
   - Expect: `ample canary next js patterns`
2. **Public-media-library self-test**  
   - Kind: `http_get`  
   - Path: `/p/public-media-library`  
   - Expect: `a CDN URL whose content is served publicly`

### 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 marketplace itself (your media processing, object layout and cache policy) is application code and was not separately tested; the pattern checks are what was verified.
- Region, compliance attestations and request-duration limits are unknown and not claimed.
- 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
- 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: 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
- Kind: `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 public-media-library and configuration-secrets. Pattern proof: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly.  
   - Observed At: 2026-09-21 02:34:39Z  
   - Expires At: 2027-03-20 02:34:39Z

### Formats
- **HTML:** [View](/content/recipes/marketplace/next-js/product-media/index.html)  
- **Markdown:** [View](/content/recipes/marketplace/next-js/product-media.md)  
- **JSON:** [View](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Amarketplace%3Anext-js%3Aproduct-media)