# Host company website with Next.js: bulk content imports

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

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

## 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

## 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`

## Success Checks
- **HTTP Get**  
  - App responds on its public URL  
    Path: `/`  
    Expect: `ample canary next js patterns`
  - Bulk-import-staging self-test  
    Path: `/p/bulk-import-staging`  
    Expect: `imported=2 rejected=1 restart=ok`

## 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 company website itself (your import format, mapping and conflict rules) is application code and was not separately tested; the pattern checks are what was verified.
- Region, compliance attestations and request-duration limits are unknown and not claimed.
- Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.
- PutObject and GetObject with path-style addressing are verified; multipart upload, listing, presigned URLs and lifecycle rules are not verified.

## Cost Estimate
- **Monthly Amount:** $10.00 (USD)  
- Based on size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty.
    - **Components**:
        - App server: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: $5.00
        - Managed PostgreSQL database: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: $5.00  
- 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.

## Evidence Summary
- **Canary Run:**  
  Next.js pattern fixture deployed on Ample (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template); checks passed for bulk-import-staging and configuration-secrets. Pattern proof: 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). Observed At: 2026-09-21T02:34:39Z

- **Last Verified At:** 2026-09-21T02:34:39Z

## Formats
- [HTML](/content/recipes/company-website/next-js/content-imports/index.html)
- [Markdown](/content/recipes/company-website/next-js/content-imports.md)
- [JSON](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Acompany-website%3Anext-js%3Acontent-imports)

## Next Actions
1. **Browse the catalog index**  
    Action ID: `browse-catalog`
2. **Search published recipes by intent, stack and constraints**  
    Action ID: `search-recipes`
3. **Prepare a side-effect-free deployment plan for an authorized project**  
    Action ID: `plan:page:recipes:company-website:next-js:content-imports`
4. **Read the existing agent authentication setup**  
    Action ID: `auth-setup`
5. **Browse Company website**  
    Action ID: `browse:workload:company-website`
6. **Browse Next.js**  
    Action ID: `browse:stack:framework-next-js`
7. **Browse Bulk import staging**  
    Action ID: `browse:pattern:bulk-import-staging`
8. **Browse Deploy web app**  
    Action ID: `browse:intent:deploy-web-app`