Drop dependency on `dotenv`?

[etagwerker]

Before we start...:

• [x] I checked the documentation and didn't find this feature
• [x] I checked to make sure that this feature has not already been requested

Branch/Commit:

main branch.

Describe the feature:

Maybe we don't need to have that dependency? At the end of the day, we use ENV to check the values associated with the environment variables. Someone could be using something else (another gem or a snippet of code) to load their env variables...

Problem:

I don't see any references to classes from the dotenv library, which leads me to believe that that dependency is not needed at all. But the gemspec file lists dotenv as a dependency.

I will abide by the code of conduct

[arielj]

I think it's a good idea to drop the dependency since... yeah, we don't really depend on Dotenv (we could also rename the gem to be EnvValidator in that case?). That will make this more generic.

Maybe we can have the option to configure the name of the file used for the configuration? Like defaulting to .env.sample but give users the option to use any file name with some configuration param in the check methods if they are using another method and a different file name makes more sense.

[cleicar]

@etagwerker @arielj sounds like a very good idea. I am all favor in always remove any unnecessary dependency.

I sadly do not have time to send a PR soon, but I can help reviewing in case you guys have it. I'm holding the announcement blogpost until we have this decided.

[etagwerker]

@cleicar @arielj After a quick poll in our internal slack, we decided to stick with dotenv_validator for now.