# Host public directory with Next.js: bulk content imports

Deploy a public directory built with Next.js on Ample using the bulk import staging 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 CSV staged as an object, row-level validation with per-row errors recorded, and a restart-safe import keyed by import id (imported=2 rejected=1 restart=ok). Not separately tested: your import format, mapping, and conflict rules; treat the public directory-specific behavior as your application code.

## Representative Queries
- Host public directory with Next.js: bulk content imports
- Where can I host public directory built with Next.js?
- I need a staged import format, validation procedure and import recovery workflow.

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

## 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 bulk import staging: a CSV staged as an object, row-level validation with per-row errors recorded, and a restart-safe import keyed by import id (imported=2 rejected=1 restart=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. `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/bulk-import-staging) from the example; then run your own checks. On failure read `ample logs --kind build` then `--kind runtime`. `ample logs --kind build`

## Examples
- **Title**: Next.js pattern fixture
  - **Description**: Multi-pattern Next.js app whose bulk import staging module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
  - **Source Ref**: tests/deploy-canaries/next-js-patterns

## Success Checks
- App responds on its public URL, expected output: `ample canary next js patterns`
- Bulk-import-staging self-test.

## 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 public directory itself (your import format, mapping and conflict rules) 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
- **Components:**
  - app server: size `s-1vcpu-1gb`, monthly amount: 5.0
  - managed PostgreSQL database: size `s-1vcpu-1gb`, monthly amount: 5.0

## Evidence Summary
- Canary run summary for Next.js pattern fixture; checks passed for bulk-import-staging and configuration-secrets.

## Next Actions
- **Browse the catalog index**: `GET /v1/catalog`
- **Search published recipes by intent, stack and constraints**: `POST /v1/catalog/search`
- **Prepare a side-effect-free deployment plan for an authorized project**: `POST /v1/catalog/plan`
- **Read the existing agent authentication setup**: `GET /mcp/setup`
- **Browse Public directory**: `GET /v1/catalog/nodes/workload%3Apublic-directory`
- **Browse Next.js**: `GET /v1/catalog/nodes/stack%3Aframework-next-js`
- **Browse Bulk import staging**: `GET /v1/catalog/nodes/pattern%3Abulk-import-staging`
- **Browse Deploy web app**: `GET /v1/catalog/nodes/intent%3Adeploy-web-app`