Re:Don’t use environment variables for configuration
by aarbor989 on Thursday April 01, 2021 @02:40AM
(#26657285)
Maybe I live under a rock, but I feel like command line utilities taking environment variable arguments just isn’t that common of a practice? The only examples I can think of are when an argument is more of a “global variable” that many different commands may find useful such as JAVA_HOME, GITHUB_TOKEN, etc. For web applications and docker containers, environment variables fit easily into the deployment process and for all intents and purposes, are pretty much static.
[ Parent
| on HN ]
Re:Don’t use environment variables for configuration
by coldtea on Thursday April 01, 2021 @02:46AM
(#26657320)
>Maybe I live under a rock, but I feel like command line utilities taking environment variable arguments just isn’t that common of a practice?
Nope, it's quite common. Many standard UNIX cli utilities take some environment variables (including things like LOCALE). Also common in scripts, setting up programming languages paths, etc.
It's also not a bad practice, contrary to what the author says.
Re:Don’t use environment variables for configuration
by saurik on Thursday April 01, 2021 @03:20AM
(#26657513)
LS_COLORS and GREP_COLORS are weirdly-specific... but arguably aren't!