# Host member portal with Next.js: private documents

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

## Representative Queries
- Host member portal with Next.js: private documents
- Where can I host Member portal built with Next.js?
- I need a role-to-document access model and negative authorization tests.

## 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.
- **S3-compatible object storage:** Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

## 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 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 (private=ok). Copy the approach into your schema; 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  --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`

## Examples
- **Next.js pattern fixture**: Multi-pattern Next.js app whose private document library module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

## Success Checks
- app responds on its public URL: `http_get` on `/` expects `ample canary next js patterns`.
- private-document-library self-test: `http_get` on `/p/private-document-library` expects `private=ok (with ?role=owner; 401 without, 403 for viewer)`.

## 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 was not separately tested; the pattern checks are what was verified.

## Cost Estimate
**Monthly Amount**: 10.0 USD  
**Components**:  
- app server (s-1vcpu-1gb) - 5.0  
- managed PostgreSQL database (s-1vcpu-1gb) - 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.

## Formats
- [HTML Version](/content/recipes/member-portal/next-js/private-documents/index.html)  
- [Markdown Version](/content/recipes/member-portal/next-js/private-documents.md)  
- [JSON API](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Amember-portal%3Anext-js%3Aprivate-documents)