Skip to content

Accept Supabase integration env var names for auth config#7

Merged
durga710 merged 1 commit into
mainfrom
claude/charming-euler-mkocv9
Jun 11, 2026
Merged

Accept Supabase integration env var names for auth config#7
durga710 merged 1 commit into
mainfrom
claude/charming-euler-mkocv9

Conversation

@durga710

Copy link
Copy Markdown
Owner

Summary

Sign-in on production fails with "Supabase Auth is not configured yet" because the deployment lacks the Supabase env vars. This makes the config reader accept both naming conventions — NEXT_PUBLIC_SUPABASE_URL/NEXT_PUBLIC_SUPABASE_ANON_KEY and the SUPABASE_URL/SUPABASE_ANON_KEY names that the Supabase Vercel integration creates — so whichever way the vars get added, auth works.

Tests pass (31/31), type-check clean.

https://claude.ai/code/session_013M57ExYGVz7k4pFXNMTBL9


Generated by Claude Code

Auth only requires NEXT_PUBLIC_SUPABASE_URL/_ANON_KEY; also accept
SUPABASE_URL/SUPABASE_ANON_KEY (the names the Supabase Vercel
integration creates) so sign-in works with either naming.

https://claude.ai/code/session_013M57ExYGVz7k4pFXNMTBL9
@vercel

vercel Bot commented Jun 11, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
ghim-tech Ready Ready Preview, Comment Jun 11, 2026 12:27am

@durga710 durga710 merged commit ea93fcc into main Jun 11, 2026
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants