Use dotenv to access env variables

[salahelfarissi]

This PR aims to use dotenv to import env variables.

[petrbroz]

Thank you @salahelfarissi. Happy to merge this one.

Btw. I'm curious - what are the main advantages of dotenv? I mean, the way I usually set env. variables is, for example:

• using my code editor (in my case with vscode launch configurations)
• using command line or bash scripts when running on remote servers
• inside Dockerfile when deploying docker containers
• using UI when deploying to AWS, Azure, Heroku, etc.

[salahelfarissi]

Hi @petrbroz. Recently I was working on integrating APS API into a React App (A monitoring plateform). We have seperate packages: api, front, ansible each having its own .env.example file.

This practice allows for better versionning, if I added a component related to APS API, I'll add its corresponding env variables along others that already exist (corresponding to db connection, AWS...) to the .env.example file, hence future developpement will concur these new env variables (developpers will be aware of their existence).

With this practice, and with the use of dotenv, to start developping you only need to:

• Copy .env.example to .env and place your env variables for each package / directory.
• Use a seperate terminal for each package (api, front...), type: yarn start loading the env variables in the cwd without starting debugging mode.

[petrbroz]

Got it, thank you @salahelfarissi! Sounds like I should consider using dotenv in my other samples as well :)