There is no reason anyone would ever use this instead of a regular config file.
God, I hate .env files
1–10 of 14 posts
Re: God, I hate .env files
#2Don't people use it with direnv?
Re: God, I hate .env files
#3What makes you believe that abruptly venting on HN will help?
Re: God, I hate .env files
#4Nothing like chasing a process.env that is undefined.
Re: God, I hate .env files
#5What makes you believe that abruptly venting on HN will help?
They are right to say it though
Re: God, I hate .env files
#6What makes you believe that abruptly venting on HN will help?
I guess they’re thinking God (https://news.ycombinator.com/user?id=God) will read their message and do something about it.
Re: God, I hate .env files
#7Same here. What I hate most is the fact how tooling decides what should be hidden files and what not. Hiding important configuration files (also done by some SSGs) is a bad habit which makes it hard to explore a new project. At least such files should be refered to in some README.
Re: God, I hate .env files
#8whats wrong with .env files?
Re: God, I hate .env files
#9I think the overuse of .env files is a side effect of the overuse of containers. Working with config files is much more convenient if you're running software normally, but if you're shipping an entire baseline OS along with your application, getting application-specific configuration data into the container becomes non-trivial. Environment variables provide a standardized way of making configuration data set outside the container available from within it.
Re: God, I hate .env files
#10How are they different than a regular config file? .env and .mytoolconfigrc seem like the same thing to me.