# Host partner portal with Next.js: private documents

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

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

## Resource Requirements
- primitive:compute
- primitive:postgres
- primitive:s3-compatible-object-storage

## Infrastructure Requirements
1. **Compute**  
   - **Status**: verified  
   - **Summary**: 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**  
   - **Status**: verified  
   - **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.

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

## 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).
- A bucket from `ample bucket create` with its credentials passed as encrypted S3_* environment variables.
- An Ample account token with servers:write, databases:read, buckets:read.

## Tested Configuration
- **Template**: node-22  
- **Runtime**: node  
- **Size**: s-1vcpu-1gb  
- **Install**: npm install  
- **Build**: npm run build --if-present  
- **Start**: npm run start

## Workflow Steps
1. **Build and start**  
   - Command: next build then next start -H 0.0.0.0 -p $PORT on the node-22 template.
2. **Implement the pattern on PostgreSQL**  
   - Description: 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). 
3. **Wire object storage**  
   - Description: 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**  
   - 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**  
   - Command: ample logs --kind build

## Success Checks
1. **App responds on its public URL**: // Expect ample canary next js patterns  
2. **Private-document-library self-test**: // Expect 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 partner portal 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  
- **Components**:  
  - App server: s-1vcpu-1gb (1.0) — $5.0  
  - Managed PostgreSQL database: s-1vcpu-1gb (1.0) — $5.0

## Evidence Summary
- Next.js pattern fixture deployed on Ample (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template).

## Next Actions
1. **Browse the catalog index**  
   - Method: GET  
   - Relative Path: /v1/catalog  
2. **Search published recipes by intent, stack and constraints**  
   - Method: POST  
   - Relative Path: /v1/catalog/search  
3. **Prepare a side-effect-free deployment plan for an authorized project**  
   - Method: POST  
   - Relative Path: /v1/catalog/plan

**Note**: The above actions will help in further exploring the available resources.