Repository navigation
fix: get the Cloudflare Worker deploy actually working - #33
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
🚀 Deploying Preview to Cloudflare 🚀Preview Deployments by commit
|
Cloudflare rejected the deploy: "Proxy (200) redirects can only point to relative paths." A static-assets Worker has no server, so it can't reverse-proxy /api/metrics/* to a different domain the way Next's rewrites() (or a real server) could -- that needs an actual Worker script, which this project deliberately doesn't have. PostHog still works: instrumentation-client.ts already reads NEXT_PUBLIC_POSTHOG_HOST directly and falls back to the real ingestion host now, so analytics aren't blocked, they're just no longer routed through our own domain to dodge ad blockers. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
vedantlavale
force-pushed
the
feat/coming-soon
branch
from
September 27, 2026 14:26
c37de05 to
e59324c
Compare
This branch was successfully deployed
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
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.
Two follow-up fixes after merging #31, found from the real Cloudflare build logs.
056acdb—mainhad no Cloudflare config at all (nowrangler.jsonc, andnext.config.tswasn't set to static export, plus it still hadredirects()/rewrites(), which Next.js refuses to build alongsideoutput: "export"). Addedoutput: "export",wrangler.jsonc, and moved the retired-route redirects + security headers topublic/_redirects/public/_headers(Cloudflare's own static-Worker convention).c37de05— the first deploy attempt got much further (build succeeded, assets uploaded) but Cloudflare rejected the_redirectsfile: "Proxy (200) redirects can only point to relative paths." The PostHog ingestion proxy (/api/metrics/* → us.i.posthog.com) doesn't work on a static-assets Worker at all — no server exists to proxy through. Dropped those 3 lines;instrumentation-client.tsalready readsNEXT_PUBLIC_POSTHOG_HOSTdirectly and falls back to the real ingestion host, so analytics still work, just not proxied through our own domain anymore.Verified locally both times:
bun run buildproduces a cleanout/with valid_redirects/_headers.🤖 Generated with Claude Code