Update supabase.yaml with variables that enable Supabase external OAu… #2162
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
|
Making Why it cannot be |
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.
It is a little bit complicated to enable Github or Google external logins w/o understanding the details of how Coolify and docker compose work. I added some variables that hopefully will help people understand how to enable these providers.
Also, normally the application or service you write sits on an url which is different from the one used by Supabase. In that case the authentication breaks because Supabase GoTrue (the auth provider) was pointing GOTRUE_SITE_URL to the Supabase service instead of the customer's application. So I fixed that and explained a bit.