Share this article
Environment Variables Almost Caused a Production Incident
The .env file was committed. Not to the public repo — to the shared internal one. By the time we caught it, three people had cloned it. Here's the exact sequence of what we did and what we changed permanently.
vivekkumarsingh.in/blog/environment-variables-production-incident
Copy link
https://vivekkumarsingh.in/blog/environment-variables-production-incident
Share on social media
Cross-post to blogging platforms
Clicking any platform copies the canonical URL to your clipboard and opens the editor. Paste it as the article's canonical URL to keep all SEO signals on this domain.
More on this subject: Software Architecture & System Design.
CloudThe internet gives you hot takes: 'Firebase is a toy' or 'AWS is overkill.' Neither is true. The right answer depends on three questions I'll walk you through — and they have nothing to do with technical preference.
9 min readCloudI pushed a feature that made one Firestore read per keystroke in a live search field. No debounce. The function triggered on every character typed. By the time I noticed, I had 40,000 reads from exactly 3 users.
5 min readCloudVercel is magical until you hit a limit you didn't anticipate. Self-hosting is flexible until it's 3 AM and something is down and nobody is on-call. Both are right for different constraints. Here's how to decide.
8 min read