# Host Community Forum with Next.js: Application Activity History

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

## Representative Queries
- Host community forum with Next.js: application activity history
- Where can I host Community forum 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
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.

## Prerequisites
- 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)
- 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**  
   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`

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

## Cost Estimate
- **Currency**: USD 
- **Monthly Amount**: $10.00 
- **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.

## 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  
   Kind: `http_get`, Path: `/`, Expect: `ample canary next js patterns`
2. Transactional-workflows self-test  
   Kind: `http_get`, Path: `/p/transactional-workflows`, Expect: `tx=ok history=2 conflict=rejected`