### Host product catalog with Nuxt: relational catalog data

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

#### Representative Queries
- Host product catalog with Nuxt: relational catalog data
- Where can I host Product catalog built with Nuxt?
- I need catalog tables, transactional update logic, and application-level access boundaries.

#### 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**  
   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
- **App responds on its public URL**  
   - **Kind:** http_get  
   - **Path:** /  
   - **Expect:** ample canary nuxt patterns

- **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 product catalog 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  
- **Basis:** size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
- **Components:**  
  - App server (s-1vcpu-1gb): $5.0  
  - Managed PostgreSQL database (s-1vcpu-1gb): $5.0  
- **Note:** Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

#### Evidence Summary
- **Canary run**: Nuxt pattern fixture deployed on Ample; checks passed for transactional-workflows and configuration-secrets.

#### Last Verified At
- 2026-09-20T03:31:44Z

#### Next Actions
- **Browse the catalog index**  
- **Search published recipes by intent**  
- **Prepare a side-effect-free deployment plan**  
- **Read the existing agent authentication setup**  
- **Browse Product catalog**  
- **Browse Nuxt**  
- **Browse Transactional workflows**  
- **Browse Deploy web app**