A better dotenv – dotenvx

.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:…

High performance secure & portable Rust functions in Node.js

"The simple way to share environment variables"

A tiny .env doctor for Node.js projects

Hey everyone, Rahim here, an indie maker with a passion for building useful tools. This time, I'm excited to share FasterNode.io: a turbo booster for your Node.js SaaS project! Think of it as a pre-built foundation packed with goodies like user auth, payments, and clean code. This means you can launch weeks, not months, faster and focus on what truly matters - building an awesome SaaS that solves problems! Whether you're a seasoned developer or just starting out, FasterNode.io is here to streamline your journey. Curious to learn more? Let's ditch the boilerplate code and build something…

Hi! I've been frustrated with the secret sharing situation in serverside javascript land for a while; the common thing is to just toss .env files around on Slack to get someone's app working, or involves some kind of convoluted setup to get a blob from a storage and turn it into environment variables via commands I have to copy paste every time. But everyone uses secret storage providers, e.g. shared password vaults, cloud secrets, etc., so why not leverage those as URIs in a JSON file that can be checked in to source control? I want something simple that would just generate the darn .env…