page:recipes:digital downloads:nuxt:relational catalog

Host digital downloads with Nuxt: relational catalog data

Deploy a digital downloads built with Nuxt on Ample using the transactional workflows 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. Verified on Nuxt: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). Not separately tested: your domain records, validation rules and concurrency policy; treat the digital downloads-specific behavior as your application code.

Representative Queries

• Host digital downloads with Nuxt: relational catalog data
• Where can I host Digital downloads built with Nuxt?
• I need catalog tables, transactional update logic and application-level access boundaries.

Resource Requirements

• Compute
• Postgres

Infrastructure Requirements

1. 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.
2. Postgres
   • Status: verified
   • Summary: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

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 PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
• An Ample account token with servers:write, databases:read

Workflow Steps

1. Build and start
   • Command: nuxt build then node .output/server/index.mjs
2. Implement the pattern on PostgreSQL
   • Description: Copy the approach into your schema; keep migrations idempotent and run them with --release-command.
3. Deploy
   • Command: ample deploy . --name --public
4. Verify
   • Command: ample logs --kind build

Example

• Nuxt pattern fixture: Multi-pattern Nuxt app whose transactional workflows module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

Success Checks

1. App responds on its public URL
   • Kind: http_get
   • Path: /
2. Transactional-workflows self-test
   • Kind: http_get
   • Path: /api/p/transactional-workflows

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 pattern checks are what was verified.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• 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.

Evidence Summary

• Kind: canary_run
  • Summary: Nuxt pattern fixture deployed on Ample.

Next Actions

• Browse the catalog index
• Search published recipes by intent, stack and constraints
• Prepare a side-effect-free deployment plan for an authorized project
• Read the existing agent authentication setup
• Browse Digital downloads
• Browse Nuxt
• Browse Transactional workflows
• Browse Deploy web app

For more details, visit the Nuxt documentation.