Match Supabase API key env names#6
Open
eltontay-circle wants to merge 3 commits into
Open
Conversation
eltontay-circle
changed the title
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
1 participant
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.
Summary
NEXT_PUBLIC_SUPABASE_PUBLISHABLE_DEFAULT_KEYto match Supabase's generated setup snippet.env.exampleto point to thesettings/api-keyspageWhy
The repo previously documented and read
NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEY, while Supabase's generated setup flow usesNEXT_PUBLIC_SUPABASE_PUBLISHABLE_DEFAULT_KEY. Renaming the repo variable removes that mismatch and makes the onboarding path line up with what developers copy from Supabase.