# Deliver public assets through CDN for Nuxt

## Summary

Cdn assets for a Nuxt app on Ample. Verified on Nuxt: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL. Build and start: nuxt build then node .output/server/index.mjs (reads HOST and PORT) on the node-22 template.

## Infrastructure requirements

- [Compute](/discover/primitive/compute): verified (Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.)
- [CDN](/discover/primitive/cdn): verified (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 (nuxt build then node .output/server/index.mjs (reads HOST and PORT) on the node-22 template)
- A bucket from `ample bucket create` with credentials passed as encrypted S3_* environment variables
- An Ample account token with servers:write, buckets:read

## Exact tested configuration

- template: `node-22`
- runtime: `node`
- size: `s-1vcpu-1gb`
- install: `npm install`
- build: `npm run build --if-present`
- start: `npm run start`

## 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. **Publish a bucket for public assets.** Publish only the asset bucket; upload versioned keys with an immutable Cache-Control header and build URLs from its public URL.

```
   ample bucket publish <bucket-name>
   ```
3. **Verify.** Fetch the live URL and /api/p/versioned-static-assets on the example; on failure read the build and runtime logs.

```
   ample logs <deployment_id> --kind build
   ```

## Tested examples

- **Nuxt pattern fixture** (tests/deploy-canaries/nuxt-patterns): Verified CDN assets on Nuxt.

## Success checks

- app responds on its public URL (`/` on the live URL, expect ample canary nuxt patterns)
- versioned-static-assets check from the example (`/api/p/versioned-static-assets` on the live URL, expect see the pattern fixture checks)

## Limitations

- Verified on the node-22 template at s-1vcpu-1gb; other sizes and Nuxt major versions are not verified.
- Region, compliance attestations and request-duration limits are unknown and not claimed.
- The CDN serves published-bucket objects only; cache rules, purge and TTL control are not verified.

## Cost estimate

Estimated 5.00 USD per month (size prices from pricing.toml at build revision a1b8c38919e59cd035ebabaced73cf84ece24371).
- app server x1 `s-1vcpu-1gb`: 5.00 USD

Always-on monthly price of the tested sizes; apps auto-pause when idle. Buckets are allocation-priced per quota and not included.

## Verification evidence

- canary_run on 2026-09-20T03:31:44Z at revision `03b6402b1b3e19178985f08ea4033804521d85d4-dirty (CLI b75e104)`: Nuxt pattern fixture deployed on Ample (nuxt build then node .output/server/index.mjs (reads HOST and PORT) on the node-22 template); for this guide: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL. (expires 2027-03-19T03:31:44Z)

Last verified: 2026-09-20T03:31:44Z

## Execution binding

MCP tool `ample_deploy` (registry `mcp:ample_deploy`), schema hash `876465fce906da0c` observed 2026-09-21T03:19:59.461917+00:00 at revision `49962bcade4f`, binding state `current`, required scopes: servers:write, buckets:read.
