## Host company website with Nuxt: public-site delivery

### Summary
Deploy a company website 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. Not separately tested: your site content and build; treat the company website-specific behavior as your application code.

### Representative Queries
- Host company website with Nuxt: public-site delivery
- Where can I host Company website built with Nuxt?
- I need an explicit origin-to-CDN delivery path and a tested public content build.

### Resource Requirements
- `primitive:compute`
- `primitive:cdn`

### Infrastructure Requirements
#### 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.

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

### Framework
- **Framework**: Nuxt
- **Workload**: Company website
- **Release Status**: published
- **Support Status**: verified
- **Execution Status**: ready

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

### Tested Configuration
- **Template**: node-22
- **Runtime**: node
- **Size**: s-1vcpu-1gb
- **Install**: npm install
- **Build**: npm run build --if-present
- **Start**: npm run start

### 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. **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 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=...`
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  --kind build` then `--kind runtime`.
   
   Command: `ample logs  --kind build`

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

### Success Checks
- **App responds on its public URL**: `http_get` path: `/`, expect: `ample canary nuxt patterns`
- **Versioned-static-assets self-test**: `http_get` path: `/api/p/versioned-static-assets`, 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 company website itself (your site content and build) is application code and was not separately tested; the pattern checks are what was verified.

### Cost Estimate
- **Currency**: USD 
- **Monthly Amount**: 5.0 
- **Basis**: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
- **Components**: 
  - **Name**: app server, **Size**: s-1vcpu-1gb, **Quantity**: 1.0, **Monthly Amount**: 5.0

### Next Actions
- **Browse the catalog index**: `GET /v1/catalog`
- **Search published recipes by intent, stack and constraints**: `POST /v1/catalog/search`
- **Prepare a side-effect-free deployment plan for an authorized project**: `POST /v1/catalog/plan`
- **Read the existing agent authentication setup**: `GET /mcp/setup`
- **Browse Company website**: `GET /v1/catalog/nodes/workload%3Acompany-website`
- **Browse Nuxt**: `GET /v1/catalog/nodes/stack%3Aframework-nuxt`
- **Browse Public web service**: `GET /v1/catalog/nodes/pattern%3Apublic-web-service`
- **Browse Deploy web app**: `GET /v1/catalog/nodes/intent%3Adeploy-web-app`