Skip to content

Move API production to Cloudflare Worker#64

Merged
hmmhmmhm merged 3 commits into
mainfrom
feat/cloudflare-supabase-geoint
Jun 2, 2026
Merged

Move API production to Cloudflare Worker#64
hmmhmmhm merged 3 commits into
mainfrom
feat/cloudflare-supabase-geoint

Conversation

@hmmhmmhm

@hmmhmmhm hmmhmmhm commented Jun 2, 2026

Copy link
Copy Markdown
Owner

Summary

  • move api.ground.codes serving to the Cloudflare Worker backed by Supabase/PostGIS
  • add API deployment workflow that refreshes changed region datasets and deploys the Worker
  • update production smoke checks for Worker readiness and add a GitHub issue fallback when Moshi webhook is not configured
  • inject runtime metadata into Worker deployments so /readyz can report the deployed commit

Verification

  • pnpm --filter api-ground-codes check-types
  • pnpm --filter api-ground-codes test
  • node --test scripts/qa-workflows.test.mjs scripts/production-smoke.test.mjs
  • pnpm --filter ground-codes build
  • pnpm production:smoke
  • GitHub Actions Production Smoke run 26813079257

hmmhmmhm added 3 commits June 1, 2026 10:54
Add a Cloudflare Worker entrypoint backed by Supabase PostGIS so the API can serve the full region dataset without Railway. Route api.ground.codes to the Worker and update production smoke checks for the new runtime.
Add an API production workflow that applies the PostGIS schema, refreshes changed region datasets in Supabase, deploys the Cloudflare Worker, and runs production smoke checks.
@hmmhmmhm hmmhmmhm merged commit 78a2169 into main Jun 2, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant