Supabase CLI setup - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the Supabase CLI used for?

The Supabase CLI is a tool that helps you manage your Supabase projects from your computer. It lets you create, develop, and deploy your database and API easily.

beginner

How do you install the Supabase CLI on your computer?

You can install the Supabase CLI by running the command npm install -g supabase-cli if you have Node.js installed. This downloads and sets up the CLI globally.

beginner

What command initializes a new Supabase project locally?

Use supabase init to create a new Supabase project folder with the necessary files to start working locally.

beginner

Why do you need to log in with the Supabase CLI?

Logging in with supabase login connects your CLI to your Supabase account, so you can manage your projects and deploy changes securely.

beginner

What is the purpose of supabase start command?

The supabase start command runs a local version of your Supabase backend, so you can test your database and API on your computer before deploying.

Which command installs the Supabase CLI globally?

A supabase setup

B supabase install

C npm install -g supabase-cli

D install supabase-cli

The correct command is npm install -g supabase-cli to install the CLI globally using Node.js.

What does supabase init do?

A Deploys your project to the cloud

B Starts the local Supabase server

C Logs you into Supabase

D Creates a new Supabase project locally

supabase init sets up a new project folder with config files to work locally.

Why should you run supabase login?

A To connect CLI with your Supabase account

B To start the local server

C To install the CLI

D To create a new project

Logging in links your CLI to your Supabase account for secure project management.

Which command runs your Supabase backend locally?

A supabase start

B supabase deploy

C supabase init

D supabase login

supabase start launches a local version of your backend for testing.

What do you need before installing the Supabase CLI with npm?

A Python installed

B Node.js installed

C Docker installed

D Java installed

Node.js is required to use npm, which installs the Supabase CLI.

Explain the steps to set up the Supabase CLI on your computer from scratch.

Think about installation, login, project creation, and running locally.

Describe why running a local Supabase backend is useful during development.

Consider benefits of local testing before cloud deployment.

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