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
Currently before sending a PR, I have to switch back to ENV=PROD from LOCAL, making it hard for the development process. This can be cumbersome, if other variables are too set this way for my local setup, and needs to be reverted back to original for sending the PR.
Expected behaviour:
This can be avoided, if we use envparse to parse the environement variables. This way it will fetch the env variable that I have set locally on my PC, instead in the project. This is also a good practice as per one of the 12 principles of 12 factors app.
The text was updated successfully, but these errors were encountered:
rupav
changed the title
use envparse or other utility like open-event instead of harcoded variables.
use envparse or other utility like in open-event instead of harcoded variables.
Oct 16, 2018
I'm submitting a ...
Current behaviour:
Currently before sending a PR, I have to switch back to
ENV=PROD
fromLOCAL
, making it hard for the development process. This can be cumbersome, if other variables are too set this way for my local setup, and needs to be reverted back to original for sending the PR.Expected behaviour:
This can be avoided, if we use envparse to parse the environement variables. This way it will fetch the env variable that I have set locally on my PC, instead in the project. This is also a good practice as per one of the 12 principles of
12 factors app
.@yashLadha @gabru-md @ParthS007 your views on this?
I would like to work on this.
The text was updated successfully, but these errors were encountered: