Environment management in Supabase - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is environment management in Supabase?

Environment management in Supabase means organizing and controlling different setups like development, testing, and production to keep your data and apps safe and separate.

beginner

Why should you separate environments like development and production?

Separating environments helps avoid mistakes that could break your live app. It lets you test changes safely without affecting real users.

intermediate

How can you manage environment variables in Supabase?

You can set environment variables in Supabase project settings to store keys and secrets safely. This keeps sensitive info out of your code.

intermediate

What is a common way to handle multiple environments in Supabase projects?

A common way is to create separate Supabase projects for each environment, like one for development and one for production, each with its own database and settings.

beginner

How does environment management improve team collaboration?

It lets team members work on features in isolated spaces without interfering with each other, making teamwork smoother and safer.

What is the main reason to use separate environments in Supabase?

A To test changes without affecting the live app

B To save money on hosting

C To make the app load faster

D To avoid writing code

Separate environments let you safely test changes without risking the live app.

Where should you store API keys in Supabase projects?

A In public folders

B Directly in the code

C In environment variables

D On paper

Environment variables keep keys secure and separate from code.

How do you create a production environment in Supabase?

A By deleting the development project

B By creating a separate Supabase project for production

C By using the same project for all environments

D By turning off the database

Separate projects keep production data safe and isolated.

What is a benefit of environment management for teams?

A Increases server costs

B Makes coding unnecessary

C Automatically fixes bugs

D Allows safe collaboration without conflicts

Teams can work independently without breaking each other's work.

Which of these is NOT a typical environment in Supabase projects?

A Marketing

B Testing

C Production

D Development

Marketing is not an environment type for managing code or data.

Explain how environment management helps keep your Supabase projects safe and organized.

Think about why you wouldn't want to test new features directly on your live app.

Describe how you would set up environment variables in Supabase and why they are important.

Consider how to keep passwords safe and not share them publicly.

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