# Host community forum with Next.js: private documents

Deploy a community forum built with Next.js on Ample using the private document library 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, a private S3-compatible bucket holds objects with credentials delivered as encrypted environment variables. Verified on Next.js: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok). Not separately tested: your identity integration and role assignments; treat the community forum-specific behavior as your application code.

## Representative Queries

- Host community forum with Next.js: private documents
- Where can I host Community forum built with Next.js?
- I need a role-to-document access model and negative authorization tests.

## Infrastructure Requirements

1. **Compute**  
   **Summary:** Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.  
   **Status:** Verified

2. **Postgres**  
   **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.  
   **Status:** Verified

3. **S3-compatible object storage**  
   **Summary:** Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.  
   **Status:** Verified

## Workflow Steps

1. **Build and start**  
   Run `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 private document library: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role. Keep migrations idempotent and run them with `--release-command`.

3. **Wire object storage**  
   Create the bucket(s), then pass endpoint, region, bucket and keys as `--env` values. Use path-style addressing. Keep private data in an unpublished bucket.

4. **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 <name> --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...`

5. **Verify**  
   Fetch the live URL and the pattern self-test route(s) `/p/private-document-library` 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 identity integration and role assignments) is application code and was not separately tested; the pattern checks are what was verified.

## Cost Estimate

- **Currency:** USD  
- **Monthly Amount:** 10.0  
- **Basis:** size prices from pricing.toml (loaded by the API)
  
   | Component                         | Size               | Quantity | Monthly Amount |
    |-----------------------------------|--------------------|----------|-----------------|
    | app server                        | s-1vcpu-1gb       | 1.0      | 5.0             |
    | managed PostgreSQL database       | s-1vcpu-1gb       | 1.0      | 5.0             |

### Evidence Summary

- The Next.js pattern fixture deployed on Ample and checks passed for private-document-library and configuration-secrets. 
- Summary includes role-to-document access model with negative tests.