Host blog with React Router: public-site delivery · Ample Computer

Host blog with React Router: public-site delivery

Deploy a blog 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. The blog-specific behavior (your site content and build) is your application code on that verified basis.

Verified November 5, 2026

What it runs on

You need

Exact tested configuration

build npm run build --if-present
install npm install
runtime node
sizes-1vcpu-1gb
start npm run start
template node-22

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 needs an answer first). Re-running with no change is a no-op.

   $ ample deploy . --name <app-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=...
  1. 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 <deployment_id> --kind build then --kind runtime.
   $ ample logs <deployment_id> --kind build

How it was checked

✓ app responds on its public URL · http get/ → “ample canary react router patterns”
✓ versioned-static-assets self-test · http get/p/versioned-static-assets → “a CDN URL whose content is served publicly”

Evidence

  1. November 5, 2026 · canary run
    React Router pattern fixture deployed on Ample (react-router build then react-router-serve on the node-22 template); checks passed for versioned-static-assets and configuration-secrets. Pattern proof: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL alongside the app's own public HTTPS URL.

  2. November 6, 2026 · canary run
    The same React Router app deployed with a --release-command migration; the marker it created was readable after activation.

Tested examples

What it doesn’t cover