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

Host company website with React Router: object-stored public media

Deploy a company website built with React Router on Ample using the public media library 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, and a published bucket serves public assets from the CDN host. Verified on React Router: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly. Not separately tested: your media processing, object layout and cache policy; treat the company website-specific behavior as your application code.

Representative Queries

Resource Requirements

Infrastructure Requirements

Primitive ID Label Status Summary
primitive:compute Compute verified Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
primitive:postgres Postgres verified Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database.
primitive:s3-compatible-object-storage S3-compatible object storage verified Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary.
primitive:cdn CDN verified The CDN host serves objects from published buckets.

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 public media library: an object written to a published bucket with an immutable Cache-Control header.

  3. Wire object storage
    Create the bucket(s), then pass endpoint, region, bucket and keys as --env values. Use path-style addressing.

  4. Deploy
    Run the synchronous deploy once and read the result.

    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=...
    
  5. Verify
    Fetch the live URL and the pattern self-test route(s). Then run your own checks.

    ample logs  --kind build
    

Examples

Success Checks

Limitations

Cost Estimate

Next Actions