feat: add support for multiple .env files #674
Conversation
AkhilJ321
requested review from
fmvilas,
Souvikns,
KhudaDad414 and
asyncapi-bot-eve
as code owners
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
|
@AkhilJ321 you have some linter issues, can you double-check it once thanks. |
Handled the linting errors,also corrected the documentation . |
| Glee has support for loading variables from `.env.local` into `process.env`. | ||
| This is useful for storing secret environment variables needed in development while keeping them out of the repository. | ||
|
|
||
| However, sometimes you might want to add some defaults for the `development` or `production` environment. You can do that by creating files with the following names: |
There was a problem hiding this comment.
please mention how the user can change the environment. (by setting NODE_ENV in their environment.)
|
|
I had some issues with github , and my forked repo got all unbalanced. So I will create a new PR after creating a new fork and making changes. |
Description
Related issue(s)
Fixes: #638