I Built My First VS Code Extension(EnvGuard) A few weeks ago, I noticed a problem that almost every...
I Built My First VS Code Extension(EnvGuard)
A few weeks ago, I noticed a problem that almost every developer faces sooner or later: configuration drift.
You add a new environment variable to your local .env file, everything works perfectly, and then deployment fails because the same variable is missing from .env.production or .env.example.
After dealing with this issue multiple times, I decided to build a solution.
Today, I'm excited to share (EnvGuard), my first published VS Code extension.
Your .env files are validated and out of Git by now, thanks to the last article on managing...
We've all done it: pasted an API key into a file "just to test," then a week later it's in your git...
A year ago I'd have told you a .env file was fine. Then we patched a CVSS 10.0 RCE in Next.js...
Environment variables are easy in local development and much harder in production. This guide covers secure configuration…
We’ve all been there. You have a dozen side projects, and your API keys, database connection strings,...
A small TypeScript CLI for syncing .env variables into GitHub Actions secrets and GitLab CI/CD variables.
