# Host project tracker with Next.js: downloadable reports

Deploy a project tracker built with Next.js on Ample using the generated downloads 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: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). Not separately tested: your export formats, retention policy and entitlement model; treat the project tracker-specific behavior as your application code.

## Representative Queries
- Host project tracker with Next.js: downloadable reports
- Where can I host Project tracker built with Next.js?
- I need an export query, generated artifact retention and authorized download flow.

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

## 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.
3. **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**: An export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3).
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**: `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/generated-downloads) from the example; then run your own checks. On failure read `ample logs  --kind build` then `--kind runtime`.

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

## Success Checks
- App responds on its public URL
- Generated-downloads self-test.

## Limitations
- Verified on the node-22 template; other sizes, templates and Next.js major versions are not verified.

## Cost Estimate
- Currency: USD
- Monthly Amount: 10.0
- Basis: size prices from pricing.toml (loaded by the API)

### Components:
- App server (size: s-1vcpu-1gb)
- Managed PostgreSQL database (size: s-1vcpu-1gb)

**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.

## Next Actions
1. **Browse the catalog index**: `GET /v1/catalog`
2. **Search published recipes**: `POST /v1/catalog/search`
3. **Prepare a side-effect-free deployment plan**: `POST /v1/catalog/plan`
4. **Read the existing agent authentication setup**: `GET /mcp/setup`
5. **Browse Project tracker**: `GET /v1/catalog/nodes/workload%3Aproject-tracker`
6. **Browse Next.js**: `GET /v1/catalog/nodes/stack%3Aframework-next-js`
7. **Browse Generated downloads**: `GET /v1/catalog/nodes/pattern%3Agenerated-downloads`
8. **Browse Deploy web app**: `GET /v1/catalog/nodes/intent%3Adeploy-web-app`