Bird
Raised Fist0
Firebasecloud~30 mins

Environment configuration in Firebase - Mini Project: Build & Apply

Choose your learning style10 modes available
LearnWhyDeepVisualTryChallengeProjectRecallTime
Environment configuration
📖 Scenario: You are setting up a Firebase project for a web app. You want to manage different environment settings for development and production to keep your app organized and safe.
🎯 Goal: Create a Firebase environment configuration that defines separate settings for development and production. This will help you switch between environments easily and keep your app secure.
📋 What You'll Learn
Create a Firebase configuration object for the development environment
Add a variable to select the current environment
Use the environment variable to choose the correct Firebase config
Export the final Firebase configuration for use in the app
💡 Why This Matters
🌍 Real World
Managing environment configurations is essential for deploying apps safely and efficiently. It helps keep development and production settings separate to avoid mistakes.
💼 Career
Cloud engineers and developers often configure environment settings to ensure apps run correctly in different stages like development, testing, and production.
Progress0 / 4 steps
1
Create the development Firebase configuration
Create a constant called firebaseConfigDev with these exact properties and values: apiKey: 'dev-api-key', authDomain: 'dev-project.firebaseapp.com', projectId: 'dev-project', storageBucket: 'dev-project.appspot.com', messagingSenderId: '1234567890', appId: '1:1234567890:web:dev'.
Firebase
Hint

Use const to create an object with the exact keys and values given.

2
Add the environment selector variable
Create a constant called currentEnv and set it to the string 'development'.
Firebase
Hint

Use const currentEnv = 'development'; to set the environment.

3
Create the production Firebase configuration and select config
Create a constant called firebaseConfigProd with these exact properties and values: apiKey: 'prod-api-key', authDomain: 'prod-project.firebaseapp.com', projectId: 'prod-project', storageBucket: 'prod-project.appspot.com', messagingSenderId: '0987654321', appId: '1:0987654321:web:prod'. Then create a constant called firebaseConfig that uses a ternary operator to select firebaseConfigDev if currentEnv is 'development', otherwise firebaseConfigProd.
Firebase
Hint

Use a ternary operator to select the config based on currentEnv.

4
Export the final Firebase configuration
Add the line export default firebaseConfig; at the end of the file to export the selected Firebase configuration.
Firebase
Hint

Use export default to make the config available to other files.

Practice

(1/5)
1. What is the main purpose of environment configuration in Firebase functions?
easy
A. To create new Firebase projects
B. To write the main logic of the function
C. To deploy the Firebase project
D. To store settings outside the code for security and flexibility

Solution

  1. Step 1: Understand environment configuration role

    Environment configuration holds settings like API keys or URLs outside the code to keep them safe and easy to change.

  2. Step 2: Compare options with this role

    Only To store settings outside the code for security and flexibility describes storing settings outside code for security and flexibility, which matches the purpose.

  3. Final Answer:

    To store settings outside the code for security and flexibility -> Option D

  4. Quick Check:

    Environment config = store settings outside code [OK]
Hint: Environment config = safe settings outside code [OK]
Common Mistakes:
  • Confusing environment config with function logic
  • Thinking environment config deploys projects
  • Mixing environment config with project creation
2. Which command correctly sets an environment variable named api.key with value 12345 in Firebase functions?
easy
A. firebase config:set api.key 12345
B. firebase functions:config:set api.key=12345
C. firebase functions:set-config api.key=12345
D. firebase functions:config add api.key 12345

Solution

  1. Step 1: Recall correct syntax for setting config

    The correct command uses 'firebase functions:config:set' followed by key=value pairs.

  2. Step 2: Match options to syntax

    Only firebase functions:config:set api.key=12345 matches the exact syntax: 'firebase functions:config:set api.key=12345'. Others have wrong commands or missing colons.

  3. Final Answer:

    firebase functions:config:set api.key=12345 -> Option B

  4. Quick Check:

    Set config = functions:config:set key=value [OK]
Hint: Use 'functions:config:set key=value' to set env vars [OK]
Common Mistakes:
  • Omitting the colon after 'functions'
  • Using spaces instead of '=' between key and value
  • Using wrong command verbs like 'add' or 'set-config'
3. Given the following commands run in order:
firebase functions:config:set service.api_key="abc123"
firebase deploy --only functions

What will functions.config().service.api_key return inside your function?
medium
A. service.api_key
B. undefined
C. "abc123"
D. null

Solution

  1. Step 1: Understand setting and deploying config

    Setting 'service.api_key' with value 'abc123' and then deploying functions makes the config available inside functions.

  2. Step 2: Accessing config in function

    Accessing 'functions.config().service.api_key' returns the string value set, which is 'abc123'.

  3. Final Answer:

    "abc123" -> Option C

  4. Quick Check:

    Config value = "abc123" after deploy [OK]
Hint: Deploy after setting config to access values [OK]
Common Mistakes:
  • Forgetting to redeploy functions after setting config
  • Expecting config to be available without deploy
  • Confusing key names or accessing wrong path
4. You set an environment variable with firebase functions:config:set db.url="https://mydb.com" but inside your function functions.config().db.url returns undefined. What is the most likely cause?
medium
A. You forgot to redeploy the functions after setting the config
B. The config key name is invalid
C. You need to restart the Firebase CLI
D. The value must be a number, not a string

Solution

  1. Step 1: Identify cause of undefined config

    Config values only update inside functions after redeploying them.

  2. Step 2: Check other options

    Key names can be strings, no CLI restart needed, and values can be strings. So these are not causes.

  3. Final Answer:

    You forgot to redeploy the functions after setting the config -> Option A

  4. Quick Check:

    Redeploy needed after config change [OK]
Hint: Always redeploy functions after config changes [OK]
Common Mistakes:
  • Assuming config updates instantly without deploy
  • Restarting CLI unnecessarily
  • Thinking config keys must be numbers
5. You want to store two environment variables for your Firebase functions: api.key with value key123 and api.secret with value secret456. Which command correctly sets both at once?
hard
A. firebase functions:config:set api.key=key123 api.secret=secret456
B. firebase functions:config:set api.key=key123; api.secret=secret456
C. firebase functions:config:set api.key=key123, api.secret=secret456
D. firebase functions:config:set api.key=key123 && api.secret=secret456

Solution

  1. Step 1: Recall syntax for multiple config keys

    Multiple keys are set by listing them separated by spaces, each as key=value pairs.

  2. Step 2: Evaluate options

    Only firebase functions:config:set api.key=key123 api.secret=secret456 uses spaces correctly. Others use semicolon, comma, or && which are invalid here.

  3. Final Answer:

    firebase functions:config:set api.key=key123 api.secret=secret456 -> Option A

  4. Quick Check:

    Multiple keys set with spaces [OK]
Hint: Separate multiple keys with spaces, not commas or semicolons [OK]
Common Mistakes:
  • Using commas or semicolons instead of spaces
  • Trying to chain commands with &&
  • Setting keys one at a time unnecessarily
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard