page:recipes:storefront:nuxt:download delivery

Host storefront with Nuxt: authorized file delivery

Deploy a storefront built with Nuxt on Ample using the generated downloads 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. Verified on Nuxt: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). Not separately tested: your export formats, retention policy and entitlement model; treat the storefront-specific behavior as your application code.

Representative Queries

• Host storefront with Nuxt: authorized file delivery
• Where can I host Storefront built with Nuxt?
• I need a file entitlement model and an application-enforced download authorization flow.

Resource Requirements

• primitive:compute
• primitive:postgres
• primitive:s3-compatible-object-storage

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.
• Postgres: 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: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

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 generated downloads: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). 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.
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=...
5. Verify: Fetch the live URL and the pattern self-test route(s) (/api/p/generated-downloads) from the example; then run your own checks. On failure read ample logs --kind build then --kind runtime.
   • Command: ample logs --kind build

Success Checks

• Check: app responds on its public URL
  • Kind: http_get
  • Path: /
  • Expect: ample canary nuxt patterns
• Check: generated-downloads self-test
  • Kind: http_get
  • Path: /api/p/generated-downloads
  • Expect: export=ok rows=3 (with ?token=...; 401 without)

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 storefront itself (your export formats, retention policy and entitlement model) is application code and was not separately tested; the pattern checks are what was verified.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Components:
  • App server: s-1vcpu-1gb (1.0) $5.00
  • Managed PostgreSQL database: s-1vcpu-1gb (1.0) $5.00
• 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.

Next Actions

• Action: Browse the catalog index
  • Method: GET
  • Relative Path: /v1/catalog
• Action: Search published recipes by intent, stack and constraints
  • Method: POST
  • Relative Path: /v1/catalog/search
  • Parameters: {"body":{"limit":5,"query":"Host storefront with Nuxt: authorized file delivery"}}
• Action: Prepare a side-effect-free deployment plan for an authorized project
  • Method: POST
  • Relative Path: /v1/catalog/plan
  • Parameters: {"body":{"inputs":{},"projectId":"","recipeId":"page:recipes:storefront:nuxt:download-delivery","recipeRevision":"r1"}}
• Action: Read the existing agent authentication setup
  • Method: GET
  • Relative Path: /mcp/setup
• Action: Browse Storefront
  • Method: GET
  • Relative Path: /v1/catalog/nodes/workload%3Astorefront
• Action: Browse Nuxt
  • Method: GET
  • Relative Path: /v1/catalog/nodes/stack%3Aframework-nuxt
• Action: Browse Generated downloads
  • Method: GET
  • Relative Path: /v1/catalog/nodes/pattern%3Agenerated-downloads
• Action: Browse Deploy web app
  • Method: GET
  • Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app