Safelaunch – Validates your environment before you push to production
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…
What it does
In the maker’s words, at launch
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.
Does the same job
all alternatives →
- PEPlaces-env, secure version control of environment files2024 · github.com · ▲6
Now that I have your attention (“Don’t you dare version control environment files!!”, “This can’t be safe.”) and before you tear me and my project to shreds, please allow me to take a moment to celebrate something small but meaningful: I’ve finally released a thing. Thank you. Motivation tl;dr: The existing tools and libraries for versioning and syncing environment files / secrets across team members and CI machines just didn’t cut it for me. So, I set out to create my own solution — one finally checks all my boxes. So what is places-env? (I encourage you to check the readme…
More dev tools this month
the category →
Open-source GTM skills for technical founders
Dev tools · 29d ago · gtmcofounder.com
OpenTrailPaper is open-source bike computer firmware for the LilyGO T5S3 4.7" E-Paper PRO. It supports offline maps, GPX routes, FIT recording and Bluetooth sensors.
Dev tools · 1d ago · opentrailpaper.com
Launched alongside, March 2026
the whole month →
Switch from ChatGPT to Claude with import memory feature
AI · Mar 2026 · claude.com
