Settings and activity
35 results found
-
2 votes
An error occurred while saving the comment Chris Barnes supported this idea ·
-
20 votes
-
8 votes
-
Crashlytics alerts do not work if Firebase permissions have been granted from Google Cloud IAM roles
11 votes -
170 votes
-
18 votes
-
18 votes
-
19 votes
-
72 votes
We are actively working on this right now. Expect an update from us shortly on how you can try out this capability.
-
133 votes
-
5 votes
-
422 votes
-
25 votes
-
10 votes
-
7 votes
-
14 votes
-
189 votes
-
21 votes
-
34 votes
-
121 votes
https://community.firebasestudio.dev/t/environment-variables/644
https://firebase.google.com/docs/studio/customize-workspace
** https://community.firebasestudio.dev/t/how-can-you-have-private-environment-variables-outside-of-dev-nix/279
-----
In Firebase Studio (previously Project IDX), environment variables are primarily managed through the .idx/dev.nix file for the development workspace and within .env files or the Firebase console for deployed services like Cloud Functions and App Hosting.
In the Firebase Studio Workspace (Development)
For variables needed within your cloud-based development environment (the workspace itself), you should use the Nix configuration file:
- Locate the file: Find the .idx/dev.nix file in the root of your project directory.
- Add variables: Within the env attribute set, define your variables. This makes them available to your workspace's terminal and processes.
For sensitive information, avoid committing these values directly to your repository. Firebase Studio is actively looking at integrating with Cloud Secret Manager for private values.
---------------
For Firebase Services (Deployment)
When deploying to Firebase services like Cloud Functions or App Hosting, there are different methods:
- Cloud Functions: You can load environment variables from a local .env file in your functions/ directory during deployment using firebase deploy --only functions. For managing secrets securely in Cloud Functions, Firebase also supports using its Secret Manager integration.
- App Hosting: Environment configuration is specified in the apphosting.yaml file. You can define variables and specify their availability (build-time, run-time, or both).
For Next.js apps on App Hosting, standard .env files also work. To make a variable accessible in the browser, you can use the NEXT_PUBLIC_ prefix, similar to local development.