page:recipes:company website:react router:public site

Host company website with React Router: public-site delivery

Deploy a company website built with React Router on Ample using the public web service pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, and a published bucket serves public assets from the CDN host. Verified on React Router: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL alongside the app's own public HTTPS URL. Not separately tested: your site content and build; treat the company website-specific behavior as your application code.

Representative Queries

Framework

Workload

Release Status

Support Status

Execution Status

Prerequisites

Tested Configuration

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. 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. Publish only the bucket that serves public assets and reference its CDN URL.
  3. 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=... --env CDN_PUBLIC_URL=...
  4. Verify

    • Fetch the live URL and the pattern self-test route(s) (/p/versioned-static-assets) from the example; then run your own checks. On failure read ample logs --kind build then --kind runtime.
    • Command: ample logs --kind build

Examples

Success Checks

Limitations

Cost Estimate

Evidence Summary

Last Verified At

Formats