Railway Deployment #2d0fc8 fix: remove broken startCommand#2
Merged
Conversation
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
The deployment fails at the healthcheck stage with
Error: '$PORT' is not a valid port number. ThestartCommandinrailway.tomlpasses$PORTas a literal string because Railway's exec-form override does not perform shell variable expansion, so gunicorn never receives the actual port number.Solution
Removed
startCommandfromrailway.tomlso the Dockerfile's CMD takes effect — it usessh -cwhich correctly expands${PORT}at runtime. Also removed thebuilder = "nixpacks"setting, which was ignored anyway since Railway auto-detects the Dockerfile. All healthcheck and restart policy settings are preserved.Changes
railway.tomlContext
ee7eccdGenerated by Railway