# Host member portal with Next.js: application activity history

Deploy a member portal built with Next.js 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 Next.js: 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 member portal-specific behavior as your application code.

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

## Resource Requirements
- primitive:compute
- primitive: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.

## Framework and Workload
- Framework: Next.js
- Workload: Member portal

## Execution Status
ready

## Prerequisites
1. A Next.js project that builds and starts with the documented commands (next build then next start -H 0.0.0.0 -p $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

## Workflow Steps
1. **Build and start**: next build then next start -H 0.0.0.0 -p $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) (/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
- **Next.js pattern fixture**: Multi-pattern Next.js 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 (http_get, path: /, expect: ample canary next js patterns)
2. transactional-workflows self-test (http_get, path: /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 Next.js major versions are not verified.
- The member 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
- **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, monthlyAmount 5.0
  - managed PostgreSQL database: size s-1vcpu-1gb, quantity 1.0, monthlyAmount 5.0
- **Note**: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

## Evidence Summary
- **Canary Run**: Next.js pattern fixture deployed on Ample (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template); checks passed for transactional-workflows and configuration-secrets. 
  - Checks: /p/transactional-workflows
  - Observed At: 2026-09-21T02:34:39Z
- Another Canary Run: The same Next.js app deployed with a --release-command migration; the marker it created was readable after activation.
  - Observed At: 2026-09-20T01:54:51Z

## Formats
- **HTML**: [View here](/content/recipes/member-portal/next-js/activity-history/index.html)
- **Markdown**: [View markdown](/content/recipes/member-portal/next-js/activity-history.md)
- **JSON**: [View JSON](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Amember-portal%3Anext-js%3Aactivity-history)

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