Environment management in Supabase - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Environment Variables in Supabase

Which of the following best describes the purpose of environment variables in a Supabase project?

A They store sensitive information like API keys and database URLs securely outside the codebase.

B They are used to write SQL queries directly inside the Supabase dashboard.

C They automatically scale the database storage based on usage.

D They provide a graphical interface to manage user authentication.

💡 Hint

Think about how you keep secrets safe when sharing your project.

Environment variables hold sensitive data such as API keys and database URLs outside the code, keeping them secure and flexible across different environments.

❓ Configuration

intermediate

Configuring Environment Variables for Local Development

You want to run your Supabase project locally with different database credentials than production. Which file should you create or modify to set these environment variables?

A .env.local

B supabase.env

C config.json

D variables.yaml

💡 Hint

Look for the standard file used by many Node.js and frontend projects for local environment variables.

The .env.local file is commonly used to set environment variables for local development, overriding defaults safely.

❓ Architecture

advanced

Managing Multiple Environments in Supabase

You have three environments: development, staging, and production. Which approach best ensures that environment variables do not leak between these environments?

A Store all environment variables in a single project and prefix keys with environment names.

B Use one Supabase project and switch environment variables manually before deployment.

C Use a shared database and rely on user roles to separate data.

D Use separate Supabase projects for each environment, each with its own environment variables.

💡 Hint

Think about isolation and risk of accidental data exposure.

Using separate Supabase projects for each environment isolates environment variables and data, preventing leaks and accidental overwrites.

❓ security

advanced

Protecting Environment Variables in Supabase

Which practice best protects environment variables containing API keys in a Supabase project?

A Share environment variable files via email to team members.

B Never commit environment variable files to version control and use a secrets manager for production.

C Store environment variables directly in the frontend code for easy access.

D Commit environment variable files but encrypt them with a password in the repo.

💡 Hint

Consider how to keep secrets safe from public access and accidental leaks.

Not committing environment files and using a secrets manager keeps sensitive data secure and reduces risk of exposure.

❓ service_behavior

expert

Effect of Changing Environment Variables on Supabase Services

After updating environment variables in the Supabase dashboard for your production project, what is the expected behavior regarding service availability?

A Environment variables cannot be changed once the project is created.

B You must manually restart services to apply the new environment variables, causing downtime.

C Supabase services automatically reload the new environment variables without downtime.

D Environment variable changes only apply after redeploying your frontend application.

💡 Hint

Think about how cloud services handle configuration updates smoothly.

Supabase reloads environment variables automatically to avoid downtime and keep services running smoothly.

Practice

1. What is the main purpose of using different environments in Supabase projects?

easy

A. To separate app setups for safety and organization

B. To increase the speed of the database

C. To reduce the size of the project files

D. To allow multiple users to edit the same data simultaneously

Solution

1. Step 1: Understand environment roles

   Different environments like development, testing, and production keep setups separate.

2. Step 2: Identify the main benefit

   This separation helps keep data safe and organized, avoiding mistakes.

3. Final Answer:

   To separate app setups for safety and organization -> Option A

4. Quick Check:

   Environment separation = safety and organization [OK]

Hint: Think safety and order when you hear 'environment' [OK]

Common Mistakes:

• Confusing environment with database speed
• Thinking environment reduces project size
• Believing environment allows simultaneous data edits

2. Which of the following is the correct way to set an environment variable in Supabase CLI?

easy

A. supabase env create API_KEY=12345

B. supabase set-env API_KEY 12345

C. supabase env add API_KEY 12345

D. supabase env set API_KEY=12345

Solution

1. Step 1: Recall Supabase CLI syntax

   The correct command to set environment variables uses 'env set' followed by key=value.

2. Step 2: Match the correct syntax

   supabase env set API_KEY=12345 matches this pattern exactly: 'supabase env set API_KEY=12345'.

3. Final Answer:

   supabase env set API_KEY=12345 -> Option D

4. Quick Check:

   Set env variable = 'env set key=value' [OK]

Hint: Remember: 'env set' plus key=value sets variables [OK]

Common Mistakes:

• Using 'set-env' instead of 'env set'
• Using 'env add' which is invalid
• Using 'env create' which is not a command

3. Given this Supabase environment setup code snippet:

supabase env list
supabase env set API_URL=https://dev.api.com
supabase env get API_URL

What will be the output of the last command?

medium

A. API_URL not found

B. https://dev.api.com

C. https://prod.api.com

D. Error: command not recognized

Solution

1. Step 1: Understand the commands

   The first command lists environment variables, the second sets API_URL to 'https://dev.api.com'.

2. Step 2: Check the get command output

   The last command retrieves the value of API_URL, which was set just before.

3. Final Answer:

   https://dev.api.com -> Option B

4. Quick Check:

   Get env variable = last set value [OK]

Hint: Get returns the last set value for the variable [OK]

Common Mistakes:

• Expecting default or production URL instead
• Thinking the variable is not found
• Assuming command syntax error

4. You tried to access an environment variable in your Supabase project but got an empty value. Which of these is the most likely cause?

medium

A. Your internet connection is down

B. You used the wrong database password

C. You forgot to set the variable using supabase env set

D. You deployed to the wrong region

Solution

1. Step 1: Identify cause of empty env variable

   An empty environment variable usually means it was never set or loaded.

2. Step 2: Match cause to options

   Forgetting to set it with 'supabase env set' is the most direct cause.

3. Final Answer:

   You forgot to set the variable using supabase env set -> Option C

4. Quick Check:

   Empty env variable = not set [OK]

Hint: Empty env? Check if you set it first [OK]

Common Mistakes:

• Blaming unrelated issues like internet or region
• Confusing env variables with database passwords
• Assuming deployment region affects env variables

5. You want to keep your production and development environments completely separate in Supabase. Which approach best achieves this?

hard

A. Create two separate Supabase projects, one for production and one for development

B. Use one project and switch environment variables manually before each deploy

C. Store all environment variables in a single file and comment out unused ones

D. Use the same database but different tables for production and development

Solution

1. Step 1: Understand environment separation needs

   Complete separation means no shared resources or data between environments.

2. Step 2: Evaluate options for separation

   Creating two separate projects ensures full isolation of data, secrets, and settings.

3. Step 3: Identify drawbacks of other options

   Switching variables manually or sharing database risks mistakes and leaks.

4. Final Answer:

   Create two separate Supabase projects, one for production and one for development -> Option A

5. Quick Check:

   Separate projects = full environment isolation [OK]

Hint: Separate projects keep environments fully isolated [OK]

Common Mistakes:

• Relying on manual variable switching
• Sharing database tables between environments
• Using one file with commented variables