Aarya Paradkar

Dotscribe - Your .env, finally explained

by
Drop in your .env file and get a fully documented version with descriptions, formats, and secret detection. No more asking the guy who left.

Add a comment

Replies

Best
Aarya Paradkar
Not every idea deserves a startup. Some just deserve to exist because the problem is real and the fix is obvious and nobody's bothered. This one: every project has a .env file. Most of them are undocumented. Half the variables have names that made sense to whoever wrote them six months ago and mean nothing to anyone onboarding now. The classic solution is "ask the person who set it up." The classic problem is that person has left, or forgotten, or is you at 11pm trying to remember what NEXT_PUBLIC_API_URL_V2_FINAL was supposed to point to. Built Dotscribe this week. Paste your .env, get every variable described — what it is, where to find it, whether it's a secret that shouldn't be committed. CLI too. npx dotscribe@latest and it runs where you are.