Skip to content

Security: Add warning — never use service_role key in client-side code #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
soloexpert wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Security: Add warning — never use service_role key in client-side code #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions .env.example
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,16 @@
# =============================================================
# SECURITY WARNING — Supabase Keys
# =============================================================
# NEVER use the service_role key here or in any client-side code.
# The service_role key bypasses ALL Row Level Security policies,
# giving anyone who visits your deployed app full admin access
# to your entire database — reads, writes, deletes, no RLS.
#
# CORRECT: use the anon/publishable key in client apps
# WRONG: VITE_SUPABASE_KEY="sbp_live_..." or service_role anywhere client-side
#
# See: https://supabase.com/docs/guides/api/api-keys
# =============================================================
VITE_SUPABASE_PROJECT_ID="your-project-id"
VITE_SUPABASE_PUBLISHABLE_KEY="your-anon-public-key"
VITE_SUPABASE_URL="https://your-project-id.supabase.co"