Repository navigation
Conversation
At the current project, we need to have a lot of .env properties based on sub-domain: master. develop. a. b. So I think it can be useful for other developers.
|
Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need the corporate CLA signed. If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks! |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks! |
|
|
||
| // https://github.com/bkeepers/dotenv#what-other-env-files-can-i-use | ||
| var dotenvFiles = [ | ||
| process.env.CUSTOM_ENV_FILE && `${process.env.CUSTOM_ENV_FILE}`, // support custom env file. Will be useful for CI |
There was a problem hiding this comment.
Please change the name of the environment variable to REACT_APP_ENV and add support for a .local env file.
|
Closing this in favour of the |
At the current project, we need to have a lot of .env properties based on sub-domain:
So I think it can be useful for other developers.
Usage example
"start": "CUSTOM_ENV_FILE=.custom.env react-scripts start"