### Host subscription content with Next.js: public product media Deploy a subscription content 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 subscription content-specific behavior as your application code. --- #### Representative Queries - Host subscription content with Next.js: public product media - Where can I host Subscription content 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 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. --- #### 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 --- #### Workflow Steps 1. **Build and start** - Command: `next build then next start -H 0.0.0.0 -p $PORT on the node-22 template.` 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** - 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** - Command: `ample logs --kind build`. --- #### Examples - **Next.js pattern fixture** Multi-pattern Next.js app whose public media library module was checked live; the module is under tests/deploy-canaries/_pattern-modules. --- #### 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 subscription content itself (your media processing, object layout and cache policy) is application code and was not separately tested; the pattern checks are what was verified. --- #### Cost Estimate - **Currency**: USD - **Monthly Amount**: 10.0 - **Basis**: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty - **Components**: - app server: s-1vcpu-1gb - Managed PostgreSQL database: s-1vcpu-1gb --- #### Evidence Summary 1. Next.js pattern fixture deployed on Ample; checks passed for public-media-library and configuration-secrets. 2. The same Next.js app deployed with a --release-command migration; the marker it created was readable after activation. --- #### Formats - **HTML**: [Link to HTML](/content/recipes/subscription-content/next-js/product-media/index.html) - **Markdown**: [Link to Markdown](/content/recipes/subscription-content/next-js/product-media.md) - **JSON**: [Link to JSON](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Asubscription-content%3Anext-js%3Aproduct-media) --- #### Next Actions 1. **Browse the catalog index** - Method: GET - Relative Path: /v1/catalog 2. **Search published recipes by intent, stack and constraints** - Method: POST - Relative Path: /v1/catalog/search - Body: {"limit":5,"query":"Host subscription content with Next.js: public product media"} 3. **Prepare a side-effect-free deployment plan for an authorized project** - Method: POST - Relative Path: /v1/catalog/plan 4. **Read the existing agent authentication setup** - Method: GET - Relative Path: /mcp/setup 5. **Browse Subscription content** - Method: GET - Relative Path: /v1/catalog/nodes/workload%3Asubscription-content 6. **Browse Next.js** - Method: GET - Relative Path: /v1/catalog/nodes/stack%3Aframework-next-js 7. **Browse Public media library** - Method: GET - Relative Path: /v1/catalog/nodes/pattern%3Apublic-media-library 8. **Browse Deploy web app** - Method: GET - Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app