fix: wrap startCommand in railway.toml with sh -c for $PORT expansion - #1
Open
railway-app[bot] wants to merge 2 commits into
Open
fix: wrap startCommand in railway.toml with sh -c for $PORT expansion#1railway-app[bot] wants to merge 2 commits into
railway-app[bot] wants to merge 2 commits into
Conversation
railway.toml startCommand overrides Dockerfile CMD shell wrapper required for \$PORT variable expansion fallback to 8000 for local runs
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
1 participant
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
Railway runs the startCommand from railway.toml in exec form for Dockerfile deployments, which bypasses shell variable expansion. The literal string
$PORTwas passed directly to uvicorn's--portflag, causing it to crash immediately withError: Invalid value for '--port': '$PORT' is not a valid integer, failing every healthcheck.Solution
Wrapped the startCommand in
/bin/sh -cso the shell expands$PORTbefore uvicorn receives it, and switched to${PORT:-8000}to provide a safe fallback for local development. This matches the pattern already used in the Dockerfile CMD.Changes
railway.tomlGenerated by Railway