It works on my machine" is still the most common deployment bug
I kept running into the same stupid deployment issue.
Everything works locally.
Tests pass.
I deploy.
Production crashes.
After digging through logs for an hour the problem ends up being something simple like:
• a missing environment variable
• something added to .env.example but not to .env
• a config mismatch between environments
The most common one for me was forgetting to add a variable locally after adding it to .env.example.
So I built a small tool to catch this instantly.
It compares .env and .env.example and tells you if something required is missing before deployment.
Example output:
deploycheck running...
Missing variables:
- DATABASE_URL
- REDIS_URL
Fix the issues above before deployment.
The idea is basically a spell checker for backend configuration mistakes.
Instead of finding out after deploy, it catches the issue while you're still working.
Right now it can:
• detect missing environment variables
• run locally as a CLI
• run in CI as a check before deployment
I’m trying to figure out if this is actually useful outside my own workflow.
Curious if others run into this problem as often as I do.
Missing variables: - DATABASE_URL - REDIS_URL
Fix the issues above before deployment. The idea is basically a spell checker for backend configuration mistakes. Instead of finding out after deploy, it catches the issue while you're still working. Right now it can: • detect missing environment variables • run locally as a CLI • run in CI as a check before deployment I’m trying to figure out if this is actually useful outside my own workflow. Curious if others run into this problem as often as I do.