Supabase CLI setup - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Supabase CLI Initialization

What is the primary purpose of running supabase init in a new project directory?

A It initializes local configuration files and folders needed for Supabase CLI to manage the project.

B It creates a new Supabase project in the cloud automatically.

C It deploys the database schema to the Supabase cloud instance.

D It installs the Supabase CLI globally on your machine.

💡 Hint

Think about what happens locally when you start using Supabase CLI in a folder.

The supabase init command sets up local files and folders that the CLI uses to manage your project. It does not create cloud projects or deploy schemas.

❓ Configuration

intermediate

Correct Supabase CLI Login Command

Which command correctly logs you into your Supabase account using the CLI?

A supabase signin

B supabase auth login

C supabase connect

D supabase login

💡 Hint

Check the official Supabase CLI command for authentication.

The command supabase login opens a browser window to authenticate your account with the CLI.

❓ Architecture

advanced

Supabase CLI Local Development Setup

After running supabase init, which folder does the CLI create to store your local database migrations and seed files?

A migrations

B supabase/migrations

C supabase/local

D db/migrations

💡 Hint

Look for the folder inside the supabase directory that holds migration files.

The CLI creates a supabase/migrations folder to keep track of database schema changes locally.

❓ security

advanced

Handling Supabase CLI Access Tokens

Where does the Supabase CLI store your access token after login, and what is the best practice for securing it?

A In a plain text file in the project folder; best practice is to add it to .gitignore.

B In environment variables; best practice is to never commit them to version control.

C In the system keychain or credential store; best practice is to use OS-level security features.

D In a hidden file in your home directory; best practice is to encrypt the file manually.

💡 Hint

Think about how CLI tools usually store sensitive tokens securely on your computer.

The Supabase CLI stores tokens securely in the OS keychain or credential store to protect them from unauthorized access.

❓ service_behavior

expert

Effect of Running supabase start Without Docker

What happens if you run supabase start on a machine where Docker is not installed or running?

A The CLI will show an error indicating Docker is required and will not start the local services.

B The CLI will start only the database service without Docker.

C The CLI will start a cloud-based Supabase instance instead of local services.

D The CLI will automatically install Docker and start the local Supabase stack.

💡 Hint

Consider what the Supabase CLI depends on to run local services.

Supabase CLI requires Docker to run local services. Without Docker, it cannot start and will show an error.

Practice

1. What is the primary purpose of the Supabase CLI?

easy

A. To manage your Supabase backend from the terminal

B. To create frontend user interfaces

C. To host websites on Supabase servers

D. To write SQL queries directly in the browser

Solution

1. Step 1: Understand Supabase CLI role

   The Supabase CLI is designed to help developers manage backend services like databases and authentication from the command line.

2. Step 2: Differentiate from frontend and hosting tools

   It does not create frontend interfaces or host websites; those are separate tasks.

3. Final Answer:

   To manage your Supabase backend from the terminal -> Option A

4. Quick Check:

   Supabase CLI = backend management [OK]

Hint: CLI means command line tool for backend tasks [OK]

Common Mistakes:

• Confusing CLI with frontend tools
• Thinking CLI hosts websites
• Assuming CLI runs in browser

2. Which command correctly installs the Supabase CLI using npm?

easy

A. npm install -g supabase

B. npm supabase install

C. install npm supabase

D. npm get supabase

Solution

1. Step 1: Recall npm global install syntax

   To install a package globally with npm, the command is npm install -g package-name.

2. Step 2: Match correct command for Supabase CLI

   The correct command is npm install -g supabase. Other options do not follow npm syntax.

3. Final Answer:

   npm install -g supabase -> Option A

4. Quick Check:

   npm install -g = global install [OK]

Hint: npm install -g for global CLI tools [OK]

Common Mistakes:

• Using wrong npm command order
• Missing -g for global install
• Typing commands in wrong sequence

3. What will happen if you run supabase start after initializing a project?

medium

A. It deploys your project to the cloud

B. It starts a local Supabase environment for testing

C. It deletes your local database

D. It opens the Supabase dashboard in a browser

Solution

1. Step 1: Understand the supabase start command

   This command launches a local Supabase environment including database and API for development and testing.

2. Step 2: Differentiate from deployment and other actions

   It does not deploy to cloud, delete data, or open dashboards automatically.

3. Final Answer:

   It starts a local Supabase environment for testing -> Option B

4. Quick Check:

   supabase start = local test environment [OK]

Hint: start means launch local environment, not deploy [OK]

Common Mistakes:

• Confusing start with deploy
• Expecting browser dashboard to open
• Thinking it deletes data

4. You run supabase init but get an error saying 'Project already initialized'. What should you do?

medium

A. Delete the existing supabase folder before reinitializing

B. Reinstall the Supabase CLI

C. Run supabase start instead to launch the environment

D. Ignore the error and continue working

Solution

1. Step 1: Understand the meaning of the error

   The error means the project was already set up with supabase init before, so reinitializing is unnecessary.

2. Step 2: Choose the correct next step

   Instead of reinitializing, you should start the local environment with supabase start.

3. Final Answer:

   Run supabase start instead to launch the environment -> Option C

4. Quick Check:

   Already initialized? Use start to run [OK]

Hint: If initialized, start instead of init again [OK]

Common Mistakes:

• Trying to init repeatedly
• Deleting files unnecessarily
• Reinstalling CLI without cause

5. You want to test changes locally and then deploy them. Which sequence of commands is correct?

hard

A. supabase start -> supabase init -> make changes -> supabase db push

B. supabase db push -> supabase start -> make changes -> supabase init

C. supabase stop -> supabase db push -> make changes -> supabase start

D. supabase init -> supabase start -> make changes -> supabase stop -> supabase db push

Solution

1. Step 1: Initialize project before starting environment

   You must run supabase init once to set up the project files before starting the local environment.

2. Step 2: Start environment, make changes, then stop and deploy

   After supabase start, you test changes locally. Then stop the environment with supabase stop before deploying with supabase db push.

3. Final Answer:

   supabase init -> supabase start -> make changes -> supabase stop -> supabase db push -> Option D

4. Quick Check:

   Init, start, test, stop, db push = correct flow [OK]

Hint: Init once, start to test, stop before db push [OK]

Common Mistakes:

• Deploying before testing locally
• Starting before initializing
• Skipping stop before deploy