Why Environment variables and secrets in Supabase? - Purpose & Use Cases

The Big Idea

What if your app's secret keys were accidentally shared with the whole world? Here's how to prevent that.

The Scenario

Imagine you have to set up your app on multiple computers by typing passwords and keys every time you start it.

You write them down in your code or share them in chat messages.

It feels like leaving your house keys under the doormat for everyone to find.

The Problem

Manually typing or storing secrets in code is slow and risky.

You might mistype a password or accidentally share it with others.

Changing a secret means updating many places, which is tiring and error-prone.

The Solution

Environment variables and secrets let you store sensitive info safely outside your code.

Your app reads them automatically when it runs, so you never expose passwords in your files.

This keeps your secrets safe and makes updates easy.

Before vs After

✗ Before

const apiKey = 'my-secret-key'; // hardcoded in code

✓ After

const apiKey = process.env.API_KEY; // loaded from environment variables

What It Enables

You can safely manage and update sensitive data without touching your code, making your app more secure and flexible.

Real Life Example

A developer deploys a Supabase app and sets the database password as a secret in the environment.

When the password changes, they update it once in the environment, and the app keeps working without code changes.

Key Takeaways

Manual secret handling risks leaks and mistakes.

Environment variables keep secrets safe outside code.

They simplify updates and improve security.

Practice

1. What is the main purpose of environment variables in Supabase?

easy

A. To display data on the website

B. To write SQL queries directly in the dashboard

C. To store important information like API keys outside the code

D. To create user accounts automatically

Solution

1. Step 1: Understand environment variables

   Environment variables hold data like API keys or URLs outside the code to keep it safe and flexible.

2. Step 2: Identify their use in Supabase

   Supabase uses environment variables to keep secrets safe and avoid hardcoding sensitive info.

3. Final Answer:

   To store important information like API keys outside the code -> Option C

4. Quick Check:

   Environment variables = store secrets safely [OK]

Hint: Environment variables keep secrets outside code [OK]

Common Mistakes:

• Thinking environment variables are for writing SQL
• Confusing environment variables with user data
• Assuming environment variables display data

2. Which is the correct way to reference an environment variable named SUPABASE_URL in a Supabase project?

easy

A. env.SUPABASE_URL()

B. process.env.SUPABASE_URL

C. getEnv('SUPABASE_URL')

D. SUPABASE_URL.value

Solution

1. Step 1: Recall environment variable syntax in JavaScript

   In JavaScript, environment variables are accessed using process.env.VARIABLE_NAME.

2. Step 2: Match with Supabase usage

   Supabase projects use this standard way to access environment variables like SUPABASE_URL.

3. Final Answer:

   process.env.SUPABASE_URL -> Option B

4. Quick Check:

   Access env vars with process.env.VAR [OK]

Hint: Use process.env.VAR to access environment variables [OK]

Common Mistakes:

• Using function calls like getEnv() which don't exist
• Trying to access variables as object properties incorrectly
• Forgetting the process.env prefix

3. Given this code snippet in a Supabase project:

const supabaseUrl = process.env.SUPABASE_URL;
const supabaseKey = process.env.SUPABASE_ANON_KEY;
console.log(supabaseUrl, supabaseKey);

What will be the output if SUPABASE_URL is set to https://xyz.supabase.co and SUPABASE_ANON_KEY is not set?

medium

A. https://xyz.supabase.co undefined

B. undefined undefined

C. https://xyz.supabase.co null

D. Error: SUPABASE_ANON_KEY not found

Solution

1. Step 1: Check environment variable values

   SUPABASE_URL is set to a URL string, but SUPABASE_ANON_KEY is missing, so it is undefined.

2. Step 2: Understand console.log output

   Logging both variables prints the URL string and undefined for the missing key.

3. Final Answer:

   https://xyz.supabase.co undefined -> Option A

4. Quick Check:

   Missing env vars print undefined [OK]

Hint: Missing env vars show as undefined in logs [OK]

Common Mistakes:

• Expecting an error when env var is missing
• Assuming missing vars print null
• Confusing undefined with empty string

4. You added a secret API_SECRET in the Supabase dashboard but your app still logs undefined when accessing process.env.API_SECRET. What is the most likely cause?

medium

A. You must include the secret in your code manually

B. The secret name is case-insensitive and should be lowercase

C. Supabase does not support environment variables

D. You forgot to restart the app after adding the secret

Solution

1. Step 1: Understand environment variable loading

   Environment variables are loaded when the app starts, so changes require a restart to take effect.

2. Step 2: Identify the cause of undefined

   If the app logs undefined, it likely did not reload the updated environment variables after adding the secret.

3. Final Answer:

   You forgot to restart the app after adding the secret -> Option D

4. Quick Check:

   Restart app to load new env vars [OK]

Hint: Restart app after adding secrets to load them [OK]

Common Mistakes:

• Thinking secret names are case-insensitive
• Believing Supabase doesn't support env vars
• Trying to hardcode secrets in code

5. You want to securely use a third-party API key in your Supabase Edge Function without exposing it in client code. Which approach is best?

hard

A. Store the API key as a secret in Supabase dashboard and access it via process.env inside the Edge Function

B. Hardcode the API key directly in the Edge Function code

C. Send the API key from the client app to the Edge Function on every request

D. Publish the API key in a public GitHub repo for easy access

Solution

1. Step 1: Understand secure storage of secrets

   Secrets like API keys should never be hardcoded or exposed publicly to avoid leaks.

2. Step 2: Use Supabase secrets in Edge Functions

   Storing the API key as a secret in the dashboard and accessing it via process.env inside the Edge Function keeps it secure and hidden from clients.

3. Final Answer:

   Store the API key as a secret in Supabase dashboard and access it via process.env inside the Edge Function -> Option A

4. Quick Check:

   Use secrets in server code, not client [OK]

Hint: Keep API keys in secrets, access only server-side [OK]

Common Mistakes:

• Hardcoding keys in code risking exposure
• Sending keys from client risking interception
• Publishing keys publicly causing leaks