# Host product catalog with Nuxt: public product media

## Summary
Deploy a product catalog built with Nuxt 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 Nuxt: 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 product catalog-specific behavior as your application code.

## Representative Queries
- Host product catalog with Nuxt: public product media
- Where can I host Product catalog built with Nuxt?
- 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**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
- **Postgres**: 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**: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary.
- **CDN**: 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 Nuxt project that builds and starts with the documented commands (nuxt build then node .output/server/index.mjs (reads HOST and 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**
   - `nuxt build then node .output/server/index.mjs (reads HOST and PORT) on the node-22 template. The server must bind 0.0.0.0 on PORT.`
2. **Implement the pattern on PostgreSQL**
   - 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.
4. **Deploy**
   - `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**
   - `ample logs  --kind build`

## Examples
- **Nuxt pattern fixture**: Multi-pattern Nuxt app whose public media library module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

## Success Checks
- **App responds on its public URL**: Expect `ample canary nuxt patterns`
- **Public-media-library self-test**: 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 Nuxt major versions are not verified.

## Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Components**:
  - app server: s-1vcpu-1gb
  - managed PostgreSQL database: s-1vcpu-1gb
  - **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.

## Next Actions
- **Browse the catalog index**: [Browse catalog index](<method>:GET, <relativePath>:/v1/catalog)
- **Search published recipes by intent, stack and constraints**: [Search recipes](<method>:POST, <relativePath>:/v1/catalog/search, <parameters>: {"body":{ "limit": 5, "query":"Host product catalog with Nuxt: public product media"}})
- **Prepare a side-effect-free deployment plan for an authorized project**: [Plan deployment](<method>:POST, <relativePath>:/v1/catalog/plan, <parameters>: {"body":{ "inputs":{}, "projectId":"", "recipeId":"page:recipes:product-catalog:nuxt:product-media", "recipeRevision":"r1"}})