Infrastructure¶

All stores run on Cloudflare's edge platform. Secrets managed in Doppler.

OFO umbrella¶

OFO is the umbrella site over all stores.

OpenFrontierOne is the GitHub org for the OFO umbrella itself. Store repos stay in their existing store orgs unless a specific repo migration is explicitly requested.

Hosting: Path B (R2)¶

Every store uses the same pattern: 1. App/game/site/agent source lives in its own GitHub repo 2. Push to main triggers GitHub Actions 3. Actions build -> upload to R2 bucket 4. Host Worker serves via wildcard subdomain (D1 route lookup -> R2 stream)

One host worker scales to thousands of subdomains without per-item CF Pages provisioning.

Per-store infrastructure¶

Secrets (Doppler)¶

• Source of truth for all infra secrets
• 8 projects (one per store), each auto-syncs to its GitHub org
• Worker secrets need both Doppler AND wrangler secret put
• GitHub rejects GITHUB_* names — use GH_* or OAUTH_*
• Full inventory: ~/dev/stores/SECRETS.md

doppler secrets --project <store> --config prd              # list
doppler secrets set KEY=value --project <store> --config prd # set
doppler secrets get KEY --project <store> --config prd --plain | ... # get (pipe only)

Package managers & tooling¶

CI/CD¶

Push to main = auto-deploy. No manual deploy commands ever needed.

Each platform monorepo has GitHub Actions workflows for: - CI (typecheck, lint, test) - Deploy per-service (backend, admin, host, agent, MCP) - Publish to npm (OIDC trusted publishing, no stored tokens) - Quality/smoke tests