Add realtime rest api to kong config #128
Merged
+27
−6
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
Contributor
|
This is great. Thanks @PatrickRogg. CC @aantti |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
What kind of change does this PR introduce?
The current kong config for realtime doesn't forward requests to the /api routes. This PR addresses this.
What is the current behavior?
Current behaviour is that everything is forwarded to
/socket. This leads to the problem that rest broadcast requests are resulting in a 404, since they are hitting/socket/api/broadcast, which doesn't exist.What is the new behavior?
Requests to the api route are forwarded correctly
Additional context
Found this in the official docker config in the supabase repo: https://github.com/supabase/supabase/blob/master/docker/volumes/api/kong.yml#L134-L174