page:recipes:product catalog:nuxt:download delivery

Host product catalog with Nuxt: authorized file delivery

Summary

Deploy a product catalog 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 product catalog-specific behavior as your application code.

Representative Queries

• Host product catalog with Nuxt: authorized file delivery
• Where can I host Product catalog 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.

Prerequisites

1. 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)
2. A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
3. A bucket from ample bucket create with its credentials passed as encrypted S3_* environment variables
4. An Ample account token with servers:write, databases:read, buckets:read

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.

   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.

   ample logs --kind build
   

Success Checks

• App responds on its public URL: Kind - http_get; Path - /; Expect - ample canary nuxt patterns.
• 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 product catalog itself (your export formats, retention policy and entitlement model) is application code and was not separately tested; the pattern checks are what was verified.
• Region, compliance attestations and request-duration limits are unknown and not claimed.
• Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.
• Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.
• PutObject and GetObject with path-style addressing are verified; multipart upload, listing, presigned URLs and lifecycle rules are not.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Basis: Size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty.
• Components:
  • App server: s-1vcpu-1gb (quantity: 1.0, monthly amount: 5.0)
  • Managed PostgreSQL database: s-1vcpu-1gb (quantity: 1.0, monthly amount: 5.0)
• 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.

Examples

1. Nuxt pattern fixture: Multi-pattern Nuxt app whose generated downloads module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
   • Source Ref: tests/deploy-canaries/nuxt-patterns

Next Actions

• Browse the catalog index: Method - GET; Relative Path - /v1/catalog.
• Search published recipes by intent, stack and constraints: Method - POST; Relative Path - /v1/catalog/search.
• Prepare a side-effect-free deployment plan for an authorized project: Method - POST; Relative Path - /v1/catalog/plan.
• Read the existing agent authentication setup: Method - GET; Relative Path - /mcp/setup.
• Browse Product catalog: Method - GET; Relative Path - /v1/catalog/nodes/workload%3Aproduct-catalog.
• Browse Nuxt: Method - GET; Relative Path - /v1/catalog/nodes/stack%3Aframework-nuxt.
• Browse Generated downloads: Method - GET; Relative Path - /v1/catalog/nodes/pattern%3Agenerated-downloads.
• Browse Deploy web app: Method - GET; Relative Path - /v1/catalog/nodes/intent%3Adeploy-web-app.