TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Better Environment Variable Management

3 pointsby jdwyahover 1 year ago

3 comments

thehucklecatover 1 year ago
I definitely feel this pain. Changing environment variables at works sucks. JIRA ticket and then back and forth with SRE about whether we really need it.<p>So it all goes in code and defeats the whole purpose of having the app be configurable.<p>I don&#x27;t know if secret management should be part of the same system though.
评论 #38530239 未加载
jdwyahover 1 year ago
We had a dynamic configuration system for much of our configuration, but it didn&#x27;t play well with environment variables.<p>And environment variables are a must, because that&#x27;s the easiest way to get terraform created config (via a configmap).<p>We updated the dynamic configuration system so that a config value can now be &quot;provided by&quot; an environment variable. This is going a long way to helping us have a much more sane single place to look to understand all our configuration.
rubyissimoover 1 year ago
This is only an issue if you have more than 1 language. Almost every language or framework has a good solution for configuration these days.