Fix Dockerfile startup command for FastAPI app - #1
Open
railway-app[bot] wants to merge 1 commit into
Open
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
The Dockerfile was using a convoluted
sh -cwrapper withpython -cto importapp.main_debugand calluvicorn.run()inline. This approach is fragile — any import error or typo in the shell-escaped string silently prevents the server from binding, causing the app to fail to respond to HTTP requests on Railway.Solution
Replaced the CMD with a clean exec-form
["uvicorn", "app.main:app", "--host", "0.0.0.0", "--port", "8000"]that targets the correct production moduleapp.main. This removes the shell indirection, eliminates the debug module dependency, and follows standard FastAPI/uvicorn deployment practice.Changes
backend/DockerfileGenerated by Railway