page:recipes:public directory:nuxt:public site
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. Not separately tested: your site content and build; treat the public directory-specific behavior as your application code.
Representative Queries
- Host public directory with Nuxt: public-site delivery
- Where can I host Public directory built with Nuxt?
- I need an explicit origin-to-CDN delivery path and a tested public content build.
Resource Requirements
- Compute
- 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. - CDN
The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.
Framework
Nuxt
Workload
Public Directory
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 createwith 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
- Build and start
Run: 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. - 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. - 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=... - 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 readample logs --kind buildthen--kind runtime.
Command: ample logs --kind build
Success Checks
- App responds on its public URL
Kind: http_get
Path: /
Expect: ample canary nuxt patterns - Versioned-static-assets self-test
Kind: 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 public directory 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.00
- Basis: size prices from pricing.toml (loaded by the API)
- Components:
- App Server:
- Size: s-1vcpu-1gb
- Quantity: 1.0
- Monthly Amount: $5.00
- App Server:
- 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
- Canary Run
Summary: Nuxt pattern fixture deployed on Ample; checks passed for versioned-static-assets and configuration-secrets. - Observed At: 2026-09-20T03:31:44Z
- Implementation Revision: 03b6402b1b3e19178985f08ea4033804521d85d4-dirty
- Expires At: 2027-03-19T03:31:44Z
Formats
Next Actions
- Browse the Catalog: API Catalog Index
- Search Recipes: Search published recipes by intent, stack, and constraints
- Prepare Deployment Plan: Deployment Plan
- Existing Auth Setup: Auth Setup
- Browse Public Directory: Public Directory
- Browse Nuxt: Nuxt
- Browse Public Web Service: Public Web Service
- Browse Deploy Web App: Deploy Web App