Skip to content

Guard staging env against inheriting the production route #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lightsofapollo merged 1 commit into from
Jun 11, 2026
Merged

Guard staging env against inheriting the production route #7

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions relay/wrangler.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,13 +56,16 @@ ALLOWED_BROWSER_ORIGINS = "https://attn.sh,https://staging.attn.sh"

# Staging deploys to a DISTINCT worker so `wrangler deploy --env staging` can
# NEVER overwrite the production "attn-relay" worker or take its relay.attn.sh
# route. Named-environment routes are not inherited from the top level, so
# staging is workers.dev-only. Durable Object namespaces are per-worker, so
# route. CAUTION: wrangler v3 DOES inherit top-level `routes` into named
# environments (observed 2026-06-10: a staging deploy attached relay.attn.sh
# to attn-relay-staging) — the explicit `routes = []` below opts staging out,
# keeping it workers.dev-only. Durable Object namespaces are per-worker, so
# staging rooms are isolated from prod. (The R2 bucket is shared by name, but
# blobs are keyed by roomId, so staging + prod objects never collide.)
[env.staging]
name = "attn-relay-staging"
workers_dev = true
routes = []

[env.staging.vars]
# vars are NOT inherited by named environments, so the full set is repeated
Expand Down
Loading