Skip to content

Commit a6188c3

Browse files
authored
docs: add section on configuring different environments for web frameworks (#8779)
1 parent dc7cac1 commit a6188c3

File tree

1 file changed

+12
-0
lines changed

1 file changed

+12
-0
lines changed

src/frameworks/docs/frameworks-overview.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -50,6 +50,18 @@ live site:
5050
1. Run `firebase deploy` from the terminal.
5151
2. Check your website on: `SITE_ID.web.app` or `PROJECT_ID.web.app` (or your custom domain, if you set one up).
5252

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+
5365
## Next steps
5466

5567
See the detailed guide for your preferred framework:

0 commit comments

Comments
 (0)