# Host Order Tracking with Nuxt: Relational Catalog Data

Deploy an order tracking app built with Nuxt on Ample using the transactional workflows pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, and 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 order tracking-specific behavior as your application code.

## Summary

- **Workload**: Order tracking  
- **Framework**: Nuxt  
- **Release Status**: Published  
- **Support Status**: Verified  
- **Execution Status**: Ready  
- **Docs Only**: false

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

## 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. An Ample account token with servers:write, databases:read.

## 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.

## 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). 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**:  
   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 order tracking itself is application code (your domain records, validation rules, and concurrency policy) and was not separately tested; the pattern checks are 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.

## Estimated Cost
- **Currency**: USD  
- **Monthly Amount**: 10.00  
- **Components**:  
   - App server: s-1vcpu-1gb, Quantity: 1, Monthly Amount: 5.00  
   - Managed PostgreSQL database: s-1vcpu-1gb, Quantity: 1, Monthly Amount: 5.00  
- Note: Always-on monthly price for tested sizes; apps and databases auto-pause when idle.

## Next Actions
1. **Browse Catalog**:  
   Action ID: browse-catalog, Method: GET, Path: `/v1/catalog`
2. **Search Recipes**:  
   Action ID: search-recipes, Method: POST, Path: `/v1/catalog/search`
3. **Prepare Deployment Plan**:  
   Action ID: plan:page:recipes:order-tracking:nuxt:relational-catalog, Method: POST, Path: `/v1/catalog/plan`
4. **Read Existing Auth Setup**:  
   Action ID: auth-setup, Method: GET, Path: `/mcp/setup`
5. **Browse Order Tracking**:  
   Action ID: browse:workload:order-tracking, Method: GET, Path: `/v1/catalog/nodes/workload%3Aorder-tracking`
6. **Browse Nuxt**:  
   Action ID: browse:stack:framework-nuxt, Method: GET, Path: `/v1/catalog/nodes/stack%3Aframework-nuxt`
7. **Browse Transactional Workflows**:  
   Action ID: browse:pattern:transactional-workflows, Method: GET, Path: `/v1/catalog/nodes/pattern%3Atransactional-workflows`
8. **Browse Deploy Web App**:  
   Action ID: browse:intent:deploy-web-app, Method: GET, Path: `/v1/catalog/nodes/intent%3Adeploy-web-app`.