Fix proxy server railway deployment #338
Merged
Conversation
This file contains 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
On Railway you need to use the PORT env var for the port
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Thanks for the PR @Henry-Pulver - we do need to simplify it as there's a couple variants floating around. Will hopefully have something more unified soon. |
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.
On Railway you need to use the PORT env var for the port
Note: not 100% sure this will actually fix the railway deployment as it's using https://github.com/BerriAI/liteLLM-proxy anyway(?) Duplication here seems confusing to you so maybe delete that one and make the 1 click deploy use this? 🤷