page:recipes:subscription content:nuxt:relational catalog

Host subscription content with Nuxt: relational catalog data

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

Representative Queries

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

Resource Requirements

• primitive:compute
• primitive:postgres

Infrastructure Requirements

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

Framework

• Nuxt

Workload

• Subscription content

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 PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
• An Ample account token with servers:write, databases: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. Implement the pattern on PostgreSQL
   The fixture's module implements transactional workflows: 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). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.
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
4. Verify
   Fetch the live URL and the pattern self-test route(s) (/api/p/transactional-workflows) 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 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: /
   Expect: ample canary nuxt patterns
2. Transactional-workflows self-test
   Kind: http_get
   Path: /api/p/transactional-workflows
   Expect: tx=ok history=2 conflict=rejected

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 subscription content itself (your domain records, validation rules and concurrency policy) 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.

Cost Estimate

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

Evidence Summary

1. Canary Run
   Summary: Nuxt pattern fixture deployed on Ample (nuxt build then node .output/server/index.mjs (reads HOST and PORT) on the node-22 template); checks passed for transactional-workflows and configuration-secrets. Pattern proof: 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).
   Observed At: 2026-09-20T03:31:44Z
   Implementation Revision: 03b6402b1b3e19178985f08ea4033804521d85d4-dirty (CLI b75e104)
   Expires At: 2027-03-19T03:31:44Z
   Scope: checks: [/api/p/transactional-workflows], pattern: pattern:transactional-workflows, template: node-22
2. Canary Run
   Summary: The same Nuxt app deployed with a --release-command migration; the marker it created was readable after activation.
   Observed At: 2026-09-20T01:54:51Z
   Implementation Revision: 199ff1dfd52683832ae75d3f98b53a7a4bff7f96-dirty (CLI e3181f5)
   Expires At: 2027-03-19T01:54:51Z
   Scope: pattern: pattern:transactional-workflows

Unknowns

• Region availability is unknown until a verified region fact is recorded
• Compliance attestations are unknown; none are claimed

Next Actions

1. Browse the catalog index
   Operation Id: catalog_index
   Method: GET
   Relative Path: /v1/catalog
   Requires Authentication: false
   Requires Approval: false
2. Search published recipes by intent, stack and constraints
   Operation Id: search_recipes
   Method: POST
   Relative Path: /v1/catalog/search
   Parameters: body: { limit: 5, query: "Host subscription content with Nuxt: relational catalog data"}
   Requires Authentication: false
   Requires Approval: false
3. Prepare a side-effect-free deployment plan for an authorized project
   Operation Id: plan_deployment
   Method: POST
   Relative Path: /v1/catalog/plan
   Parameters: body: { inputs: {}, projectId: "", recipeId: "page:recipes:subscription-content:nuxt:relational-catalog", recipeRevision: "r1"}
   Requires Authentication: true
   Requires Approval: false
4. Read the existing agent authentication setup
   Operation Id: existing_auth_setup
   Method: GET
   Relative Path: /mcp/setup
   Requires Authentication: false
   Requires Approval: false
5. Browse Subscription content
   Operation Id: browse_node
   Method: GET
   Relative Path: /v1/catalog/nodes/workload%3Asubscription-content
   Parameters: nodeId: workload:subscription-content
   Requires Authentication: false
   Requires Approval: false
6. Browse Nuxt
   Operation Id: browse_node
   Method: GET
   Relative Path: /v1/catalog/nodes/stack%3Aframework-nuxt
   Parameters: nodeId: stack:framework-nuxt
   Requires Authentication: false
   Requires Approval: false
7. Browse Transactional workflows
   Operation Id: browse_node
   Method: GET
   Relative Path: /v1/catalog/nodes/pattern%3Atransactional-workflows
   Parameters: nodeId: pattern:transactional-workflows
   Requires Authentication: false
   Requires Approval: false
8. Browse Deploy web app
   Operation Id: browse_node
   Method: GET
   Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app
   Parameters: nodeId: intent:deploy-web-app
   Requires Authentication: false
   Requires Approval: false