Skip to content

chore(dev): allow extra dev origins via DEV_ALLOWED_ORIGINS - #371

Merged
hturnbull93 merged 1 commit into
mainfrom
dev-allowed-origins-env
Oct 23, 2026
Merged

hturnbull93 merged 1 commit into
mainfrom
dev-allowed-origins-env

Conversation

@hturnbull93

Copy link
Copy Markdown
Collaborator

Next's dev server refuses its hot-reload (HMR) connection from hosts that aren't in allowedDevOrigins, so a dev preview opened on another host name (for me, the machine's tailnet name, from my phone) loads but never hot-reloads.

DEV_ALLOWED_ORIGINS (comma-separated hosts) is now added to allowedDevOrigins. Unset, behaviour is unchanged. My agent pods set it to the tailnet host.

Dev only: allowedDevOrigins has no effect on production builds.

🤖 Generated with Claude Code

Next's dev server refuses its hot-reload connection from hosts not in
allowedDevOrigins, so a preview opened on another host (e.g. a tailnet
name) needed a manual refresh after each change. Comma-separated hosts
in DEV_ALLOWED_ORIGINS are now allowed too; unset, nothing changes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@railway-app

railway-app Bot commented Oct 23, 2026 •

Copy link
Copy Markdown

🚅 Deployed to the catalyse-pr-371 environment in PauseAI Catalyse

Service Status Web Updated
web 🕒 Building (View Logs) Web Oct 23, 2026 at 3:22 pm UTC

@railway-app
railway-app Bot temporarily deployed to PauseAI Catalyse / catalyse-pr-371 October 23, 2026 15:22 Destroyed
@hturnbull93
hturnbull93 merged commit 85d12a0 into main Oct 23, 2026
3 of 4 checks passed

This branch was successfully deployed

No deployments
PauseAI Catalyse / catalyse-pr-371 — ca701fa0 Deployed Oct 23, 2026 by railway-app[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant