Repository navigation
Expand file tree
/
Copy path.env.example
More file actions
31 lines (29 loc) · 1.64 KB
/
Copy path.env.example
File metadata and controls
31 lines (29 loc) · 1.64 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
# Copy to .env.local and fill in. .env.local is git-ignored; this file is not, so
# never put a real secret here.
#
# The values below are safe to commit and should work as-is. They are not generated
# per machine or per project: the local stack's keys are string constants compiled
# into the Supabase CLI binary itself, so every contributor's `supabase start` prints
# these exact values. The CLI version is pinned in pnpm-lock.yaml, which is what keeps
# that true — one more thing gained by having it as a devDependency rather than a
# global install.
#
# They protect nothing. The stack they open is bound to 127.0.0.1 on a developer's
# own machine.
#
# `pnpm exec supabase status` reprints them at any time.
#
# For the hosted project, take them from the Supabase dashboard under
# Project Settings -> API keys.
# The REST endpoint. http://127.0.0.1:54321 locally; https://<ref>.supabase.co hosted.
NEXT_PUBLIC_SUPABASE_URL=http://127.0.0.1:54321
# The publishable key (`sb_publishable_...`), successor to the legacy `anon` JWT.
# NEXT_PUBLIC_ on purpose: this key is meant to reach the browser, and row level
# security — not secrecy — is what protects the data behind it. Proxying reads through
# a server action to hide it would buy nothing.
#
# There is a second key in the dashboard, the secret key (`sb_secret_...`, formerly
# `service_role`). It bypasses RLS entirely, so every policy is decorative to anything
# holding it. It must never appear in this file, never carry a NEXT_PUBLIC_ prefix, and
# never be imported by a client component or by any module one can reach.
NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEY=sb_publishable_ACJWlzQHlZjBrEguHvfOxg_3BJgxAaH