## Host partner portal with Nuxt: application activity history

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

### Representative Queries
- Host partner portal with Nuxt: application activity history
- Where can I host Partner portal built with Nuxt?
- I need an application-owned event schema and tested history queries; not native platform audit logs.

### Resource Requirements
- Compute
- 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
- **Partner portal**

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

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

### MCP Binding
- **Registry Ref**: mcp:ample_deploy
- **Tool Name**: ample_deploy
- **Schema Hash**: 876465fce906da0c224d62961d3343064108ebe30af80cf1b87094974e948853
- **Observed At**: 2026-09-21T03:19:59.461917+00:00
- **Implementation Revision**: 49962bcade4f
- **Required Scopes**: [servers:write, databases:read]
- **Binding State**: current

### Unknowns
- Region availability is unknown until a verified region fact is recorded.
- Compliance attestations are unknown; none are claimed.

### Formats
- **HTML**: https://ample.computer/recipes/partner-portal/nuxt/activity-history
- **Markdown**: https://ample.computer/recipes/partner-portal/nuxt/activity-history.md
- **JSON**: https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Apartner-portal%3Anuxt%3Aactivity-history

### Next Actions
1. **Browse the catalog index**: GET /v1/catalog 
2. **Search published recipes by intent, stack and constraints**: POST /v1/catalog/search (Query: Host partner portal with Nuxt: application activity history)
3. **Prepare a side-effect-free deployment plan for an authorized project**: POST /v1/catalog/plan
4. **Read the existing agent authentication setup**: GET /mcp/setup
5. **Browse Partner portal**: GET /v1/catalog/nodes/workload%3Apartner-portal
6. **Browse Nuxt**: GET /v1/catalog/nodes/stack%3Aframework-nuxt
7. **Browse Transactional workflows**: GET /v1/catalog/nodes/pattern%3Atransactional-workflows
8. **Browse Deploy web app**: GET /v1/catalog/nodes/intent%3Adeploy-web-app