Repository navigation
fix(website): bind ema.tnsor.network as the worker's custom domain in config - #832
Merged
Merged
Conversation
… config The deploy never attaches the domain: nothing in wrangler.jsonc asked for it, and the dashboard attachment went to a different worker (a staging OnlyGPUs app holds ema.tnsor.network and serves its homepage while every other path 404s). Declaring the route with custom_domain makes every deploy idempotently attach the domain to nostream-website — last writer wins, so CI redeploys self-heal the binding instead of relying on a one-time dashboard click. Requires the deploy token to carry Workers Domains:Edit (attach may fail with an auth error if not; the run log will name it).
🦋 Changeset detectedLatest commit: 32242d0 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
 [High impact] The PR appears safe to merge, with the token permission requirement already acknowledged.
|
cameri
approved these changes
Oct 15, 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.
Problem
ema.tnsor.network serves OnlyGPUs' staging app, not the nostream site. Verified: homepage HTML canonical → onlygpus.com, OnlyGPUs title; /changelog, /docs/*, /favicon.webp all 404 with Astro's default 404 page; favicon.svg (OnlyGPUs') 200s.
Root cause: nothing binds the domain to nostream-website. The deploy workflow's wrangler step only uploads the worker (its log shows workers.dev URL only, no domain attach), and the dashboard attachment made yesterday landed on a different worker. A Workers custom domain binds exactly one worker — last writer wins — so the fix is to make the deploy own the binding.
Fix
wrangler.jsonc now declares:
json routes: [{ pattern: ema.tnsor.network, custom_domain: true }]With this, every deploy idempotently (re)attaches ema.tnsor.network to nostream-website — the binding self-heals on each deploy instead of depending on a one-time dashboard action.
Requirement
The
websiteenvironment's CLOUDFLARE_API_TOKEN must carry Workers Domains: Edit (account-level). It already has Workers Scripts: Edit (proven by the successful 81-asset upload). If the attach step fails with an auth error, that permission is the one to add to the token.Verification
routes[].custom_domainexists and is required).