Environment configuration in Firebase - Step-by-Step Execution

Process Flow - Environment configuration

Start

↓

Create .env file

↓

Add environment variables

↓

Use variables in firebase config

↓

Deploy or run locally

↓

Firebase reads env variables

↓

App uses config values

↓

End

This flow shows how environment variables are created, added to Firebase config, and used during deployment or local run.

Execution Sample

Firebase

FIREBASE_API_KEY=abc123
FIREBASE_AUTH_DOMAIN=myapp.firebaseapp.com
firebase deploy

Defines environment variables and deploys Firebase app using those variables.

Process Table

Step	Action	Environment Variable State	Firebase Behavior	Result
1	Create .env file	No variables yet	No config available	File created, empty
2	Add FIREBASE_API_KEY	FIREBASE_API_KEY=abc123	Config updated with API key	API key ready for use
3	Add FIREBASE_AUTH_DOMAIN	FIREBASE_API_KEY=abc123, FIREBASE_AUTH_DOMAIN=myapp.firebaseapp.com	Config updated with auth domain	Auth domain ready for use
4	Run firebase deploy	Variables loaded from .env	Firebase reads env variables	App deployed with correct config
5	App starts	Variables accessible in app	App initializes with config	App connects to Firebase services
6	End	Variables remain accessible	Firebase services running	App fully functional

💡 Deployment completes and app runs using environment variables from .env file

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
FIREBASE_API_KEY	undefined	abc123	abc123	abc123	abc123
FIREBASE_AUTH_DOMAIN	undefined	undefined	myapp.firebaseapp.com	myapp.firebaseapp.com	myapp.firebaseapp.com

Key Moments - 3 Insights

Why do we need a .env file instead of hardcoding variables?

Using the .env file keeps sensitive info like API keys out of code, and lets Firebase read them securely during deploy (see execution_table steps 2-4).

What happens if environment variables are missing during deploy?

Firebase won't have the needed config, so the app may fail to connect to services (see execution_table step 4 where variables must be loaded).

Are environment variables accessible after deployment?

Yes, they remain accessible to the app at runtime for configuration (see execution_table steps 5-6).

Visual Quiz - 3 Questions

Look at the execution_table, what is the state of FIREBASE_API_KEY after step 3?

A abc123

B myapp.firebaseapp.com

C undefined

D empty string

💡 Hint

Check the 'Environment Variable State' column at step 3

At which step does Firebase read the environment variables?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Look at the 'Firebase Behavior' column for when variables are loaded

If FIREBASE_AUTH_DOMAIN was not added in step 3, what would happen at step 5?

A App connects normally

B App fails to initialize auth domain

C Firebase deploy fails

D No effect on app

💡 Hint

Refer to variable_tracker and execution_table steps 3 and 5

Concept Snapshot

Environment configuration in Firebase:
- Store sensitive keys in a .env file
- Add variables like FIREBASE_API_KEY and FIREBASE_AUTH_DOMAIN
- Firebase reads these during deploy
- App uses variables at runtime
- Keeps config secure and flexible

Full Transcript

Environment configuration in Firebase involves creating a .env file to store sensitive information like API keys and auth domains. These variables are added step-by-step and loaded by Firebase during deployment. The app then accesses these variables at runtime to connect to Firebase services securely. This method avoids hardcoding secrets and allows easy updates without changing code.