Repository navigation
Railway Deployment #ed2a57 fix: Force Node provider in Railpack - #7
Merged
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
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
Railpack detected Python from the new root pyproject.toml and uv.lock, found no web entry point, and failed the build with "No start command detected". The deployable app is the Next.js site.
Solution
Added railpack.json with provider set to node, so Railpack builds with npm run build and starts with npm run start (next build, next start) and ignores the Python files used only by CI.
Changes
railpack.jsonContext
58ea963Generated by Railway