# Host Order Tracking with Nuxt: Public Product Media

Deploy an order tracking 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 order tracking-specific behavior as your application code.

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

## Resource Requirements
- Compute
- Postgres
- S3-compatible object storage
- CDN

## Infrastructure Requirements
### Compute
- **Label:** 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
- **Label:** 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
- **Label:** 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
- **Label:** 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 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**  
   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) (/api/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

## 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.  
   Kind: http_get  
   Path: /  
   Expect: ample canary nuxt patterns

- Public-media-library self-test.  
   Kind: http_get  
   Path: /api/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 Nuxt major versions are not verified.
- The order tracking 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:  
    - Size: s-1vcpu-1gb  
    - Quantity: 1.0  
    - Monthly Amount: 5.0  
  - Managed PostgreSQL Database:  
    - Size: 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:** Nuxt pattern fixture deployed on Ample; 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-20T03:31:44Z

## Formats
- HTML: [Link](/content/recipes/order-tracking/nuxt/product-media/index.html)
- Markdown: [Link](/content/recipes/order-tracking/nuxt/product-media.md)
- JSON: [Link](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Aorder-tracking%3Anuxt%3Aproduct-media)