Firebase CLI setup - Commands & Configuration

Introduction

Setting up the Firebase CLI lets you manage your Firebase projects from your computer. It helps you deploy apps, manage databases, and configure services easily without using the web console.

When you want to deploy a web or mobile app to Firebase hosting from your computer.

When you need to initialize a new Firebase project with default settings.

When you want to manage Firebase services like Firestore or Functions using command line.

When you want to test Firebase features locally before publishing.

When you want to update your Firebase project configuration quickly without using the web interface.

Commands

This command installs the Firebase CLI globally on your computer so you can use it anywhere.

Terminal

npm install -g firebase-tools

Expected Output

+ firebase-tools@latest

added 50 packages from 30 contributors in 10s

This command logs you into your Firebase account so the CLI can access your projects.

Terminal

firebase login

Expected Output

✔  Success! Logged in as [e-mail]

This command starts the setup for a new Firebase project in your current folder, letting you choose features to use.

Terminal

firebase init

Expected Output

You're about to initialize a Firebase project in this directory:



? Which Firebase CLI features do you want to set up for this folder? Press Space to select features, then Enter to confirm your choices.

? Select features: Hosting: Configure files for Firebase Hosting and (optionally) set up GitHub Action deploys



=== Hosting Setup

? What do you want to use as your public directory? public

? Configure as a single-page app (rewrite all urls to /index.html)? Yes

? Set up automatic builds and deploys with GitHub? No



Firebase initialization complete!

This command uploads your app and configuration to Firebase so it becomes live on the internet.

Terminal

firebase deploy

Expected Output

=== Deploying to 'your-project-id'...



i  deploying hosting



✔  hosting: example-project-1234.web.app

✔  hosting: example-project-1234.firebaseapp.com



✔  Deploy complete!



Project Console: https://console.firebase.google.com/project/your-project-id/overview

Key Concept

If you remember nothing else from this pattern, remember: the Firebase CLI lets you control your Firebase projects easily from your computer with simple commands.

Common Mistakes

Trying to run Firebase CLI commands without installing firebase-tools first.

The commands won't work because the CLI program is not available on your computer.

Always run 'npm install -g firebase-tools' first to install the CLI.

Running 'firebase deploy' before logging in with 'firebase login'.

The CLI cannot access your Firebase projects without login, so deployment fails.

Run 'firebase login' and complete authentication before deploying.

Not selecting the correct features during 'firebase init'.

Your project may miss important setup files or configurations needed for your app.

Carefully choose the features you need during initialization, like Hosting or Firestore.

Summary

Install Firebase CLI globally using npm to get access to Firebase commands.

Log in to your Firebase account with 'firebase login' to connect the CLI to your projects.

Initialize your project folder with 'firebase init' to set up Firebase features.

Deploy your app and settings to Firebase with 'firebase deploy' to make it live.

Practice

1. What is the main purpose of the Firebase CLI tool?

easy

A. To create Firebase projects online automatically

B. To write Firebase database rules only

C. To manage Firebase projects from your computer

D. To replace the Firebase console website

Solution

1. Step 1: Understand Firebase CLI role

   The Firebase CLI is a command-line tool that lets you control Firebase projects locally on your computer.

2. Step 2: Compare options

   Options B, C, and D describe limited or incorrect roles. Only To manage Firebase projects from your computer correctly states the main purpose.

3. Final Answer:

   To manage Firebase projects from your computer -> Option C

4. Quick Check:

   Firebase CLI = Manage projects locally [OK]

Hint: Firebase CLI controls projects from your PC, not just online [OK]

Common Mistakes:

• Thinking Firebase CLI only edits database rules
• Believing it creates projects automatically online
• Confusing it with the Firebase web console

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

easy

A. install firebase-cli -npm

B. npm install -g firebase-tools

C. npm firebase install -g

D. firebase install npm-tools

Solution

1. Step 1: Recall npm install syntax

   The correct npm command to install a global package is 'npm install -g package-name'.

2. Step 2: Match with Firebase CLI package

   The Firebase CLI package name is 'firebase-tools', so the correct command is 'npm install -g firebase-tools'.

3. Final Answer:

   npm install -g firebase-tools -> Option B

4. Quick Check:

   npm install -g firebase-tools = Correct install command [OK]

Hint: Use 'npm install -g firebase-tools' to install globally [OK]

Common Mistakes:

• Mixing order of npm and firebase keywords
• Forgetting the '-g' flag for global install
• Using incorrect package names

3. What will happen if you run firebase init in your project folder?

medium

A. It deploys your app to Firebase hosting immediately

B. It deletes all Firebase projects linked to your account

C. It logs you out of Firebase CLI

D. It initializes Firebase in the folder by creating config files

Solution

1. Step 1: Understand 'firebase init' purpose

   This command sets up Firebase in your local folder by creating necessary config files and asking which Firebase features to enable.

2. Step 2: Eliminate wrong options

   Options A, B, and D describe actions unrelated to initialization. Deploying is done with 'firebase deploy', not 'init'.

3. Final Answer:

   It initializes Firebase in the folder by creating config files -> Option D

4. Quick Check:

   firebase init = Setup project locally [OK]

Hint: 'firebase init' sets up config files, not deploy or delete [OK]

Common Mistakes:

• Confusing 'init' with 'deploy'
• Thinking it deletes projects
• Assuming it logs out the user

4. You ran firebase deploy but got an error saying 'No Firebase project detected'. What is the likely cause?

medium

A. You did not run firebase init to set up the project

B. You forgot to install Node.js on your computer

C. You are not logged into Firebase CLI

D. Your internet connection is offline

Solution

1. Step 1: Analyze error message

   The error 'No Firebase project detected' means the CLI cannot find project config files in the folder.

2. Step 2: Identify missing setup step

   Without running 'firebase init', the project folder lacks Firebase config files, causing this error.

3. Final Answer:

   You did not run firebase init to set up the project -> Option A

4. Quick Check:

   Missing init causes 'No Firebase project detected' error [OK]

Hint: Run 'firebase init' before deploy to create config files [OK]

Common Mistakes:

• Assuming login or internet issues cause this error
• Ignoring the need to initialize project first
• Thinking Node.js installation affects this error

5. You want to deploy only your Firebase Functions without affecting Hosting or Firestore. Which command should you use?

hard

A. firebase deploy --only functions

B. firebase deploy --only hosting

C. firebase deploy --only firestore

D. firebase deploy --all

Solution

1. Step 1: Understand deploy options

   The Firebase CLI allows deploying specific services using the '--only' flag followed by the service name.

2. Step 2: Select correct service for Functions

   To deploy only Functions, use '--only functions'. Other options deploy different services or all.

3. Final Answer:

   firebase deploy --only functions -> Option A

4. Quick Check:

   Deploy specific service with '--only functions' [OK]

Hint: Use '--only functions' to deploy just Functions [OK]

Common Mistakes:

• Using '--only hosting' or '--only firestore' by mistake
• Using '--all' deploys everything, not just Functions
• Not using '--only' flag and deploying all services