Repository navigation
feat: serve www and docs from Cloudflare Workers - #364
Merged
Merged
Conversation
simonvanlierde
force-pushed
the
feat/sites-on-workers
branch
from
September 28, 2026 15:30
4054f4b to
1df47c0
Compare
- deploy-sites.yml builds both sites and deploys them to Workers static assets on every release, weekly from the latest release, and by hand per environment - infra/cloudflare binds their hostnames as Workers Custom Domains instead of tunnel routes, and writes the Worker names and account id into the GitHub Environments - an Astro integration per site writes the `_headers` file that replaces the Caddyfile; the header tests move onto it - drop the www and docs production images, Caddyfiles, compose services and smoke tests; their Dockerfiles keep only the dev target
… headers - the staging Environment requires a reviewer, since its Workers token is account-wide and could deploy prod's Workers; infra/cloudflare refuses to apply staging without one - deploy-sites serializes per Worker instead of per calling workflow, and the weekly run skips releases that predate the Workers deploy - scripts/check_site_headers.sh serves the built site under wrangler dev before each deploy and checks its headers, 404 page and method handling - the cutover runbook writes the Environment variables before Deploy Sites needs them; the install guide drops the removed tunnel targets and covers hosting the sites without Cloudflare - images-verify checks only the images that are still published
simonvanlierde
force-pushed
the
feat/sites-on-workers
branch
from
September 28, 2026 15:37
1df47c0 to
8eb9329
Compare
- the dev stage is now the whole image, so it needs its own non-root USER; node owns the sources, the site directory and node_modules for Vite's cache - start astro directly: `pnpm exec` re-verified the lockfile and installed the whole workspace on every container start
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
1 participant
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.
The landing page and docs move off the deploy hosts onto Cloudflare Workers static assets, deployed from CI on every release and weekly, so they stay up independently of the host and the landing hero refreshes without a release. Stacked on #362.
infra/cloudflarebinds their hostnames as Workers Custom Domains and writes the Worker names into the GitHub Environments_headersfile, with the existing header tests ported to it