feat(deploy): migrate static site delivery to Cloudflare Workers#13
Merged
bubunyo merged 1 commit intoJul 12, 2026
Merged
Conversation
Collaborator
Author
|
Can you check it out @bubunyo |
Elvis020
force-pushed
the
feature/cloudflare-static-assets
branch
2 times, most recently
from
964641b to
10465ea
Compare
bubunyo
reviewed
Jul 10, 2026
bubunyo
requested changes
Jul 10, 2026
Keep GitHub Pages and Cloudflare Workers as independent deployment workflows during the migration. Each workflow owns its triggers, build, concurrency group, permissions, and deploy target, so removing the Cloudflare workflow cannot change GitHub Pages behavior. Add Cloudflare Workers Static Assets configuration, a pinned Wrangler 4.107.1 deployment action, local deploy scripts, automatic trailing-slash handling, and administrator cutover guidance. Preserve static-only behavior: no runtime server entrypoint, API, authentication, or database binding is introduced. The existing Nuxt website Worker remains untouched until a later deliberate retirement. Record pnpm approvals for esbuild, sharp, and workerd so clean CI installs can execute Wrangler's trusted native runtime dependency. Verified both workflow YAML files, CI=true pnpm install --frozen-lockfile, pnpm deploy:dry-run, and local Workers Assets smoke tests returning 200 for public and meetup routes and 404 for an unknown route.
Elvis020
force-pushed
the
feature/cloudflare-static-assets
branch
from
10465ea to
b11b20f
Compare
bubunyo
approved these changes
Jul 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DevCongress website migration plan
This is a staged migration of the DevCongress website into one Cloudflare-hosted product.
The immediate goal is to run the existing static Astro website on Cloudflare Workers alongside GitHub Pages, without changing what visitors see.
Roadmap
devcongress.orgto the Worker. Keep GitHub Pages active during the soak period.This PR — Phase 1: Static hosting
Objective
Deploy the existing static Astro build through Cloudflare Workers Static Assets while keeping GitHub Pages current as the parallel deployment and rollback path.
In scope
dist/output.main, scheduled refreshes, and manual workflow runs.Out of scope
devcongress.orgcutover.Implementation
devcongress-websitewebsite— unchanged; appears to be the older Nuxt deploymentcloudflare-workers-productionpnpm deploy:dry-runpnpm deployThe Worker serves static assets only. No Worker server entrypoint, API route, authentication, Supabase integration, or database binding is introduced.
Verification completed
pnpm deploy:dry-run200200200404Admin decision required
Worker name
Cloudflare already has a Worker named
website, which appears to be the older Nuxt deployment.This PR uses
devcongress-websiteso the new Astro website can be tested without overwriting that Worker.Please confirm one option @bubunyo:
devcongress-websitefor the migration Worker.website-staticfor a simpler temporary name.websiteonly when we are ready to intentionally replace or retire the Nuxt Worker.Admin setup required before merge
Create this GitHub environment:
cloudflare-workers-production
Add these environment secrets:
Restrict the API token to the DevCongress Cloudflare account and zone.
Do not commit either value to the repository.