checking-env-config

Use when you want to know what configuration a service needs, why a deploy fails on a missing setting, whether .env.example is up to date, or before a first deploy.

Provide the project path. You do not have to prepare the missing-name list in advance. The tool reads repository files only and does not need network access or real .env files. Nothing was installed or run here.

The post describes missingenv comparing what code reads with Docker, Compose, and Kubernetes files, names only, and links this repository. Run the bundled script on the path, then check high findings in the code and ask where production config lives if it may be outside the repo. Documented commands were not executed here.

A missing name in the repo does not prove it is missing in production. Never open real .env files or print values; unused findings can be libraries reading a name you did not match. Do not edit config or deploy files unless asked. Scripts were not executed. MIT requires notices and gives no warranty. GitHub login GillMacedo and X handle giumacedo differ; the public mapping is submitted, not auto-approved. When fixing .env.example, add names with empty values and do not copy real values into it. A variable name can still be sensitive, so treat the output like source code.