Show HN: I just fixed .env once and for all – better-env

better-env.dev

6 points by harish3304 3 hours ago

.env files have always felt archaic, insecure, clunky and honestly just not fun to work with. I see my friends (and myself) accidentally committing them all the time. Managing secrets across projects becomes a mess of copy-pasting keys into scattered env files with no real way to sync anything.

So I built better-env: a secure, developer-friendly alternative to .env.

Store your secrets once in a global encrypted store, and load them per-project at runtime.

I’d love feedback on whether this feels useful beyond solo devs, and what you’d want for teams or CI setups.

Fully open source: https://github.com/HarishChandran3304/better-env

robinroy03 3 hours ago

I was searching for something like this. So will other developers of the repo also need the tool?

  • harish3304 3 hours ago

    Yes, they can just clone and directly run the app with their own set of secrets if better-env is set up.