You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/frameworks/docs/frameworks-overview.md
+12Lines changed: 12 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -50,6 +50,18 @@ live site:
50
50
1. Run `firebase deploy` from the terminal.
51
51
2. Check your website on: `SITE_ID.web.app` or `PROJECT_ID.web.app` (or your custom domain, if you set one up).
52
52
53
+
## Configure different environments
54
+
55
+
You can deploy multiple sets of environment variables for different project environments, such as staging and production.
56
+
57
+
Like Cloud Functions for Firebase, this tooling supports the [dotenv](https://www.npmjs.com/package/dotenv) file format for loading environment variables specified in a .env file.
58
+
59
+
* If you have a `staging` project alias, you can deploy environment variables from a `.env.staging` file.
60
+
* If you have a `production` project alias, you can deploy environment variables from a `.env.production` file.
61
+
* If you have a project with id `PROJECT_ID`, you can deploy environment variables from a `.env.PROJECT_ID` file.
62
+
63
+
See the [Cloud Functions documentation](https://firebase.google.com/docs/functions/config-env?gen=2nd#deploying_multiple_sets_of_environment_variables) for a detailed guide.
64
+
53
65
## Next steps
54
66
55
67
See the detailed guide for your preferred framework:
0 commit comments