# Host public directory with Nuxt: public-site delivery

Deploy a public directory built with Nuxt on Ample using the public web service pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, and a published bucket serves public assets from the CDN host. Verified on Nuxt: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL alongside the app's own public HTTPS URL. The public directory-specific behavior (your site content and build) is your application code on that verified basis.

Verified November 6, 2026

## What it runs on

- [Computeverified](/content/discover/primitive/compute/index.html)  
  Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

- [CDNverified](/content/discover/primitive/cdn/index.html)  
  A published bucket's objects are served from its public URL; set Cache-Control when uploading to control caching. App responses are served by the app.

## You need

- 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 bucket from `ample bucket create` with its credentials passed as encrypted S3_* environment variables
- An Ample account token with servers:write, buckets:read

## Exact tested configuration

- build npm run build --if-present
- install npm install
- runtime node
- sizes-1vcpu-1gb
- start npm run start
- template node-22

## 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. **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.

3. **Deploy.** Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 needs an answer first). Re-running with no change is a no-op.
   
   ```
   $ ample deploy . --name <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=...
   ```

4. **Verify.** Fetch the live URL and the pattern self-test route(s) (/api/p/versioned-static-assets) from the example; then run your own checks. On failure read `ample logs <deployment_id> --kind build` then `--kind runtime`.
   
   ```
   $ ample logs <deployment_id> --kind build
   ```

## How it was checked

✓ app responds on its public URL· http get/ → “ample canary nuxt patterns”  
✓ versioned-static-assets self-test· http get/api/p/versioned-static-assets → “a CDN URL whose content is served publicly”

## Evidence

1. November 6, 2026 · canary run  
   Nuxt pattern fixture deployed on Ample (nuxt build then node .output/server/index.mjs (reads HOST and PORT) on the node-22 template); checks passed for versioned-static-assets and configuration-secrets. Pattern proof: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL alongside the app's own public HTTPS URL.
2. November 5, 2026 · canary run  
   The same Nuxt app deployed with a --release-command migration; the marker it created was readable after activation.

## Tested examples

- **Nuxt pattern fixture.** Multi-pattern Nuxt app whose public web service module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

## What it doesn’t cover

- Verified on the node-22 template at s-1vcpu-1gb with the example fixture.
- The pattern checks verified the platform side; the public directory itself (your site content and build) is your application code.
- Buckets speak the standard S3 API (PutObject and GetObject with path-style addressing are checked by the fixture); `ample bucket upload-url` returns presigned upload URLs.
- The CDN serves published-bucket objects; control caching with Cache-Control on upload and versioned keys.
