# Host storefront with Nuxt: relational catalog data

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

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

## Resource Requirements
- **Compute**: Primitive
- **Postgres**: Primitive

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

## 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 storefront 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**  
     - **Size**: s-1vcpu-1gb  
     - **Quantity**: 1.0  
     - **Monthly Amount**: 5.0  
  - **Managed PostgreSQL database**  
     - **Size**: 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. 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.
   - **Observed At**: 2026-09-20T03:31:44Z  
   - **Expires At**: 2027-03-19T03:31:44Z
   - **Scope**:  
     - **Checks**: [/api/p/transactional-workflows]

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  
   - **Expires At**: 2027-03-19T01:54:51Z
   - **Scope**:  
     - **Pattern**: pattern:transactional-workflows

## Next Actions
1. **Browse the catalog index**  
   - **Operation ID**: catalog_index  
   - **Method**: GET
   - **Relative Path**: /v1/catalog

2. **Search published recipes by intent, stack and constraints**  
   - **Operation ID**: search_recipes  
   - **Method**: POST
   - **Relative Path**: /v1/catalog/search

3. **Prepare a side-effect-free deployment plan for an authorized project**  
   - **Operation ID**: plan_deployment  
   - **Method**: POST
   - **Relative Path**: /v1/catalog/plan

4. **Read the existing agent authentication setup**  
   - **Operation ID**: existing_auth_setup  
   - **Method**: GET
   - **Relative Path**: /mcp/setup

5. **Browse Storefront**  
   - **Operation ID**: browse_node  
   - **Method**: GET
   - **Relative Path**: /v1/catalog/nodes/workload%3Astorefront

6. **Browse Nuxt**  
   - **Operation ID**: browse_node  
   - **Method**: GET
   - **Relative Path**: /v1/catalog/nodes/stack%3Aframework-nuxt

7. **Browse Transactional workflows**  
   - **Operation ID**: browse_node  
   - **Method**: GET
   - **Relative Path**: /v1/catalog/nodes/pattern%3Atransactional-workflows

8. **Browse Deploy web app**  
   - **Operation ID**: browse_node  
   - **Method**: GET
   - **Relative Path**: /v1/catalog/nodes/intent%3Adeploy-web-app