fix(deploy): read port from .env instead of inherited DISPATCH_PORT#8
Merged
Merged
Conversation
Deploy health checks were failing because agent shells inherit DISPATCH_PORT from when they were spawned, which may be stale (e.g. 8787 after the default changed to 6767). The scripts now read the port from the server's .env file as the authoritative source, falling back to DEFAULT_PORT only if .env is missing. Co-Authored-By: Claude Opus 4.6 <[email protected]>
selfcontained
force-pushed
the
fix/deploy-health-port-resolution
branch
from
March 10, 2026 03:50
84ad91b to
601407b
Compare
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.
Summary
DISPATCH_PORTfrom spawn time, which can be stale after a port default changedispatch-deploy,dispatch-server,dispatch-release) now read the port from the server's.envfile as the authoritative sourceDEFAULT_PORTonly if.envis missingTest plan
resolve_portreturns 6767 from.enveven whenDISPATCH_PORT=8787is in the environmentlaunchctl unload/loadrestart cycle: server came back healthy on attempt 3 (~5s)🤖 Generated with Claude Code