page:recipes:client portal:nuxt:activity history

Host Client Portal with Nuxt: Application Activity History

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

Representative Queries

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

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

Resource Requirements

Compute
Postgres

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

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

Description: Multi-pattern Nuxt app whose transactional workflows module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
Source Reference: tests/deploy-canaries/nuxt-patterns

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 client portal 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:
- App server: s-1vcpu-1gb, quantity: 1.0, monthly amount: 5.0
- 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

Nuxt pattern fixture deployed on Ample: Deploy 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
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

Last Verified At

2026-09-20T03:31:44Z

Unknowns

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

Formats

Next Actions

Browse the catalog index: GET /v1/catalog
Search published recipes by intent, stack and constraints: POST /v1/catalog/search
- Body: {"limit":5,"query":"Host client portal with Nuxt: application activity history"}
Prepare a side-effect-free deployment plan for an authorized project: POST /v1/catalog/plan
- Body: {"inputs":{},"projectId":"","recipeId":"page:recipes:client-portal:nuxt:activity-history","recipeRevision":"r1"}
Read the existing agent authentication setup: GET /mcp/setup
Browse Client portal: GET /v1/catalog/nodes/workload%3Aclient-portal
Browse Nuxt: GET /v1/catalog/nodes/stack%3Aframework-nuxt
Browse Transactional workflows: GET /v1/catalog/nodes/pattern%3Atransactional-workflows
Browse Deploy web app: GET /v1/catalog/nodes/intent%3Adeploy-web-app