Repository navigation
dotenv-safe instead of manual checking a hardcodet whitelist #111
Description
Maybe its an idea to use dotenv-safe, with that you can define the needed env variables in the .env.example (the optional ones can be prefixed with # ).
Reacted by Samuel Batista and Enrique Bermúdez
Reacted by Enrique Bermúdez
Activity
bhgsbatista commentedon Aug 27, 2019
I second this, less code, less things to think about. The .
gitignoreexample file would also need to be fixed, since it currently ignores.env*files.