Environment management in Supabase - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the environment variable for the Supabase URL.

Supabase

export SUPABASE_URL=[1]

Drag options to blanks, or click blank then click option'

Ahttps://api.supabase.io

Bhttps://your-project.supabase.co

Clocalhost:5432

Dhttp://127.0.0.1

Attempts:

3 left

💡 Hint

Common Mistakes

Using localhost or IP address instead of the Supabase project URL.

Omitting the https:// prefix.

The SUPABASE_URL environment variable must be set to your project's unique URL provided by Supabase.

2fill in blank

medium

Complete the code to set the environment variable for the Supabase API key.

Supabase

export SUPABASE_KEY=[1]

Drag options to blanks, or click blank then click option'

Ayour-secret-api-key

Bpublic-anonymous-key

C123456

Dapikey

Attempts:

3 left

💡 Hint

Common Mistakes

Using the public anonymous key instead of the secret key.

Using a placeholder or incomplete key.

The SUPABASE_KEY must be set to your project's secret API key for authentication.

3fill in blank

hard

Fix the error in the environment variable export command for Supabase URL.

Supabase

export SUPABASE_URL=[1]

Drag options to blanks, or click blank then click option'

A"https://your-project.supabase.co"

Byour-project.supabase.co

Chttps://your-project.supabase.co

Dhttps://your-project.supabase.co/

Attempts:

3 left

💡 Hint

Common Mistakes

Not using quotes causing syntax errors.

Including trailing slashes that might cause issues.

When exporting environment variables in shell, the URL should be enclosed in quotes to avoid errors if it contains special characters.

4fill in blank

hard

Fill both blanks to initialize the Supabase client with environment variables.

Supabase

const supabase = createClient([1], [2]);

Drag options to blanks, or click blank then click option'

Aprocess.env.SUPABASE_URL

Bprocess.env.SUPABASE_KEY

CSUPABASE_URL

DSUPABASE_KEY

Attempts:

3 left

💡 Hint

Common Mistakes

Using raw strings instead of environment variables.

Mixing up URL and key positions.

The Supabase client requires the URL and API key from environment variables accessed via process.env.

5fill in blank

hard

Fill all three blanks to create a secure environment configuration file for Supabase.

Supabase

module.exports = {
  supabaseUrl: [1],
  supabaseKey: [2],
  options: { schema: [3] }
};

Drag options to blanks, or click blank then click option'

Aprocess.env.SUPABASE_URL

Bprocess.env.SUPABASE_KEY

C'public'

D'private'

Attempts:

3 left

💡 Hint

Common Mistakes

Hardcoding sensitive keys instead of using environment variables.

Using incorrect schema names.

This configuration exports environment variables for URL and key, and sets the schema to 'public' for default database access.

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