Use env variables from config instead of directly from process

[GHkrishna]

Prerequisites
CREDEBL Platform setup

Current behavior
Currently all the env variables are used using process.env which is not the best scenario in case of inappropriate values

Expected behavior
Check existence of env variables and add required validations in a config file

Desktop

• OS:
• CREDEBL Version: v2.0.0

[rockito10]

Hello, I wanted to ask if I could get this issue assigned. Im kind of a beginner on this and wanted to try with basic issues to see if I can handle some. Thanks!

[GHkrishna]

Hello @rockito10 ,
The issue is still open, you can create a draft PR, mention the issue and start with the changes.

[rockito10]

Hi, I wanted to ask which kind of validations you would like for each env variable (as in, if it matches the correct type and/or regex check), and, if it doesnt pass the validation, should I throw an error? Thanks!

[GHkrishna]

Yes sure, depending on the variables we can have validations either based on its type or regex or both, whatever is required.
Yes, we can throw appropriate error to support early failure.

You can refer the CREDEBL Docs to understand more about what variables are absolutely necessary. There's also a demo env to get more info

[rockito10]

Hello, another question:
In cases like these .env variables
PUBLIC_DEV_API_URL=https://devapi.credebl.id
is checking if PUBLIC_DEV_API_URL is an URL enough, or should it follow https://devapi.credebl.id/somethingelse (as a regex, for example)
Thanks! Im close to finishing this, sorry if I'm taking too long.

[GHkrishna]

For now, validating if it's a URL should be enough.
That's okay, just a suggestion to have a draft PR mentioning the issue, with whatever code you have would be really helpful for other contributors to understand you are working on it

[rockito10]

Sure, I will look into it, sorry if it was misleading. Thank you!