# Host company website with React Router: bulk content imports

Deploy a company website built with React Router 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 React Router: 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 React Router: bulk content imports
- Where can I host Company website built with React Router?
- I need a staged import format, validation procedure and import recovery workflow.

## Prerequisites
- A React Router project that builds and starts with the documented commands (react-router build then react-router-serve 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**  
   react-router build then react-router-serve 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.  
   Command: `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`.  
   Command: `ample logs  --kind build`

## Examples
### React Router pattern fixture
- **Description**: Multi-pattern React Router app whose bulk import staging module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
  
  **Source Reference**: tests/deploy-canaries/react-router-patterns

## Success Checks
- **App responds on its public URL**  
   Kind: http_get  
   Path: /  
   Expect: ample canary react router patterns  
- **Bulk-import-staging self-test**  
   Kind: http_get  
   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 React Router 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.