### Host campaign site with React Router: bulk content imports

#### Summary
Deploy a campaign site 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 campaign site-specific behavior as your application code.

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

#### Input Schema
```json
{
  "env": [
    "VAR1=value1",
    "VAR2=value2"
  ],
  "name": "my-app",
  "path": "/path/to/project",
  "release_command": "npm run migrate"
}
```

#### Tested Configuration
- Template: node-22
- Runtime: node
- Size: s-1vcpu-1gb
- Install: `npm install`
- Build: `npm run build --if-present`
- Start: `npm run start`

#### Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0 
- **Components**:
  - **App Server**: s-1vcpu-1gb - $5.00
  - **Managed PostgreSQL Database**: s-1vcpu-1gb - $5.00

Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

#### 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 campaign site itself (your import format, mapping, and conflict rules) is application code and was not separately tested; the pattern checks are what was verified.
