Skip to content

Category

Config tools.

Catch configuration drift between your code and its environment files.

1toolAll tools

Config tools

  • ConfigLive

    Env Example Checker

    Find env vars your code uses but .env.example is missing.

    Paste your code and your .env.example to find environment variables used in code but missing from the example (and unused keys). Pure client-side.

    Open tool

When you reach for Config tools.

Configuration drift is the failure mode where nothing is broken and everything is. The code reads an environment variable that was added three sprints ago; .env.example never learned about it; a new developer clones the repo, follows the README exactly, and gets a runtime error that names a variable they have never heard of.

It is nobody's fault and nobody's job, which is why it persists. The example file is documentation that is never executed, so nothing enforces it.

This compares what the code actually reads against what the example file actually declares, in both directions — missing keys that will break a fresh setup, and stale keys that will send someone hunting for a variable nothing uses any more.

Back to all tools