Host public directory with React Router: bulk content imports

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

Representative Queries

• Host public directory with React Router: bulk content imports
• Where can I host Public directory built with React Router?
• 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.

Execution Status

• Release Status: published
• Support Status: verified
• Execution Status: ready

Prerequisites

1. A React Router project that builds and starts with the documented commands (react-router build then react-router-serve on the node-22 template).
2. A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env).
3. A bucket from ample bucket create with its credentials passed as encrypted S3_* environment variables.
4. An Ample account token with servers:write, databases:read, buckets:read.

Tested Configuration

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

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

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

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Components:
  • App server (size: s-1vcpu-1gb, quantity: 1.0, monthly amount: 5.0)
  • Managed PostgreSQL database (size: s-1vcpu-1gb, quantity: 1.0, monthly amount: 5.0)
• 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

• Kind: canary_run
  • Summary: React Router pattern fixture deployed on Ample; 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-20T03:31:44Z
  • Implementation Revision: 03b6402b1b3e19178985f08ea4033804521d85d4
  • Expires At: 2027-03-19T03:31:44Z

Next Actions

• Actions to utilize:
  • Browse the catalog index.
  • Search published recipes by intent, stack and constraints.
  • Prepare a side-effect-free deployment plan for an authorized project.
  • Read the existing agent authentication setup.
  • Browse Public directory.
  • Browse React Router.
  • Browse Bulk import staging.
  • Browse Deploy web app.