Zengtudor/Nuxt
1
0
Fork 0
mirror of https://github.com/nuxt/nuxt.git synced 2024-11-22 21:55:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: add note that .env is not read in production (#4714)

Browse Source
This commit is contained in:
Daniel Roe 2022-04-29 20:09:12 +02:00 committed by GitHub
parent 68384b58f4
commit ff60e9f97c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/content/2.guide/2.features/10.runtime-config.md
View File

@ -33,10 +33,15 @@ console.log(runtimeConfig.public.apiBase)
### Environment Variables
The most common way to provide configuration is by using [Environment Variables](https://medium.com/chingu/an-introduction-to-environment-variables-and-how-to-use-them-f602f66d15fa).
::alert{type=info}
Nuxt CLI has built-in [dotenv](https://github.com/motdotla/dotenv) support.
In addition to any process environment variables, if you have a `.env` file in your project root directory, it will be automatically loaded into `process.env` and accessible within your `nuxt.config` file and modules.
However, **after your project is built**, you are responsible for setting environment variables when you run the server - your `.env` file will not be read at this point.
::
Runtime config values are automatically replaced by matching environment variables at runtime. For this to work, you _must_ have a fallback value (which can just be an empty string) defined in your `nuxt.config`.
**Example:**