Host blog with React Router: public-site delivery

Summary

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. Not separately tested: your site content and build; treat the blog-specific behavior as your application code.

Representative Queries

• Host blog with React Router: public-site delivery
• Where can I host Blog built with React Router?
• I need an explicit origin-to-CDN delivery path and a tested public content build.

Resource Requirements

• primitive:compute
• primitive:cdn

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.

  • Status: verified
  • More info

• CDN: The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

  • Status: verified
  • More info

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 bucket from ample bucket create with its credentials passed as encrypted S3_* environment variables
• An Ample account token with servers:write, 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. 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

• React Router pattern fixture: Multi-pattern React Router app whose public web service module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

Success Checks

• App responds on its public URL
  • Kind: http_get
  • Path: /
  • Expect: ample canary react router patterns
• Versioned-static-assets self-test
  • Kind: http_get
  • Path: /p/versioned-static-assets
  • Expect: a CDN URL whose content is served publicly

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 blog itself (your site content and build) 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.
• PutObject and GetObject with path-style addressing are verified; multipart upload, listing, presigned URLs and lifecycle rules are not.
• The CDN serves published-bucket objects only; cache rules, purge and TTL control are not verified.

Cost Estimate

• Currency: USD
• Monthly Amount: 5.0
• Authoritative: true
• Basis: size prices from pricing.toml (loaded by the API)
  • Components:
    • Name: app server
      • Size: s-1vcpu-1gb
      • Quantity: 1.0
      • Monthly Amount: 5.0
  • Note: Always-on monthly price of the tested sizes; buckets are allocation-priced per quota and not included.

Next Actions

1. Browse the catalog index: GET
2. Search published recipes by intent, stack and constraints: POST
3. Prepare a side-effect-free deployment plan for an authorized project: POST
4. Read the existing agent authentication setup: GET
5. Browse Blog: GET
6. Browse React Router: GET
7. Browse Public web service: GET
8. Browse Deploy web app: GET