fix: render backend issues#51
Merged
mr-jones123 merged 1 commit intomainfrom Nov 1, 2025
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
This pull request updates the backend API to support deployment on Render and Vercel, and refactors the frontend chat hook to use a consistent endpoint environment variable. The most significant changes are the addition of a health check endpoint, expanded CORS support for Vercel deployments, and simplification of the chat hook configuration.
Backend API improvements:
GET /) tosrc/api/main.pyfor Render deployment monitoring.allow_originsto include all Vercel preview deployments (https://*.vercel.app) insrc/api/main.py.Frontend chat hook refactor:
useStreamingChatinsrc/hooks/useStreamingChat.tsto useNEXT_PUBLIC_RENDER_ENDPOINTas the default endpoint, falling back tohttp://localhost:8000. Removed theapiUrlparameter to simplify usage.useStreamingChatto use the newendpointvariable instead of the previousapiUrlparameter. [1] [2]