# Host admin dashboard with Next.js: public profile assets

Deploy an admin dashboard built with **Next.js** on Ample using the public image delivery 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, and a published bucket serves public assets from the CDN host.  
Verified on Next.js: public objects in a published bucket served from the CDN URL, kept separate from private objects in an unpublished bucket that require authorization (private=ok only for the allowed role). Not separately tested: your image processing and profile-media rules; treat the admin dashboard-specific behavior as your application code.

## Representative Queries
- Host admin dashboard with Next.js: public profile assets  
- Where can I host Admin dashboard built with Next.js?  
- I need separate public profile media from private data, with CDN cache rules.

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

## 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.
4. **CDN**  
   - Status: Verified  
   - Summary: The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

## 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 public image delivery: public objects in a published bucket served from the CDN URL, kept separate from private objects in an unpublished bucket that require authorization (private=ok only for the allowed role). 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. Keep private data in an unpublished bucket. Publish only the bucket that serves public assets and reference its CDN URL.
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.
5. **Verify**  
   - Fetch the live URL and the pattern self-test route(s) (/p/public-media-library, /p/private-document-library) from the example; then run your own checks. On failure read `ample logs  --kind build` then `--kind runtime`.

## 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 admin dashboard itself (your image processing and profile-media rules) is application code and was not separately tested; the pattern checks are what was verified.  
- Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.

## Next Actions
- **Browse the catalog index**  
   - **GET** /v1/catalog  
- **Search published recipes**  
   - **POST** /v1/catalog/search  
- **Prepare a side-effect-free deployment plan**  
   - **POST** /v1/catalog/plan