[PR #76] [CLOSED] add supabase auth (default remains no auth) #141

New Issue

2026-02-16T10:16:16-05:00

yindo commented

2026-02-16 10:16:16 -05:00

📋 Pull Request Information

Original PR: https://github.com/langgenius/webapp-conversation/pull/76
Author: @somethingwentwell
Created: 6/4/2024
Status: ❌ Closed

Base: main ← Head: add-supabase-auth

📝 Commits (1)

13c6b6c add supabase auth

📊 Changes

9 files changed (+181 additions, -18 deletions)

View changed files

📝 .env.example (+6 -0)
📝 .vscode/settings.json (+1 -1)
📝 README.md (+4 -0)
➕ README_SUPABASE_AUTH.md (+60 -0)
📝 app/page.tsx (+78 -11)
📝 config/index.ts (+2 -2)
➕ docker-compose.yml (+13 -0)
📝 package.json (+7 -4)
➕ utils/supabaseClient.ts (+10 -0)

📄 Description

This pull request introduces the capability to enable Supabase authentication in our application. By leveraging Supabase auth, we can now support both traditional email & password authentication as well as various social login methods.

Changes:
Added environment variables to configure Supabase auth:

NEXT_PUBLIC_ENABLE_SUPABASE_AUTH: Set to false by default, meaning no authentication is required. If set to true, Supabase auth will be enabled.
NEXT_PUBLIC_SUPABASE_URL: Configuration for the Supabase URL, defaulted to http://localhost:8000 for development purposes.
NEXT_PUBLIC_SUPABASE_ANON_KEY: The anonymous key necessary for Supabase operations, to be replaced with the actual key in production.

Implementation:
The implementation checks the NEXT_PUBLIC_ENABLE_SUPABASE_AUTH variable. If it's true, the application initializes Supabase client with the provided URL and anonymous key, thus enabling the email & password and social logins supported by Supabase.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/langgenius/webapp-conversation/pull/76 **Author:** [@somethingwentwell](https://github.com/somethingwentwell) **Created:** 6/4/2024 **Status:** ❌ Closed **Base:** `main` ← **Head:** `add-supabase-auth` --- ### 📝 Commits (1) - [`13c6b6c`](https://github.com/langgenius/webapp-conversation/commit/13c6b6cf8ac4cc8d2758720c325ee3fa33a2f659) add supabase auth ### 📊 Changes **9 files changed** (+181 additions, -18 deletions) <details> <summary>View changed files</summary> 📝 `.env.example` (+6 -0) 📝 `.vscode/settings.json` (+1 -1) 📝 `README.md` (+4 -0) ➕ `README_SUPABASE_AUTH.md` (+60 -0) 📝 `app/page.tsx` (+78 -11) 📝 `config/index.ts` (+2 -2) ➕ `docker-compose.yml` (+13 -0) 📝 `package.json` (+7 -4) ➕ `utils/supabaseClient.ts` (+10 -0) </details> ### 📄 Description This pull request introduces the capability to enable Supabase authentication in our application. By leveraging Supabase auth, we can now support both traditional email & password authentication as well as various social login methods. **Changes:** Added environment variables to configure Supabase auth: - NEXT_PUBLIC_ENABLE_SUPABASE_AUTH: Set to false by default, meaning no authentication is required. If set to true, Supabase auth will be enabled. - NEXT_PUBLIC_SUPABASE_URL: Configuration for the Supabase URL, defaulted to http://localhost:8000 for development purposes. - NEXT_PUBLIC_SUPABASE_ANON_KEY: The anonymous key necessary for Supabase operations, to be replaced with the actual key in production. **Implementation:** The implementation checks the NEXT_PUBLIC_ENABLE_SUPABASE_AUTH variable. If it's true, the application initializes Supabase client with the provided URL and anonymous key, thus enabling the email & password and social logins supported by Supabase. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

yindo added the pull-request label 2026-02-16 10:16:16 -05:00

yindo closed this issue

2026-02-16 10:16:16 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: langgenius/webapp-conversation#141