Como usar: .env.example Generator
- Paste your
.env(it never leaves the browser), or switch to From source code and paste code. - Secrets such as keys, tokens, passwords and connection strings are blanked; safe values like
PORT=3000are kept. - Review the summary of what was removed, kept and flagged.
- Copy or download the
.env.exampleand commit it.
Why commit a .env.example?
A .env file holds secrets and must never be committed. But new team members, CI and deployment platforms still need to know which variables exist. A .env.example (also called .env.sample or .env.template) lists every key with placeholder values and comments, so anyone can copy it to .env and fill in their own values.
How secrets are detected
- Key names containing SECRET, TOKEN, PASSWORD, PASS, PWD, KEY, PRIVATE, CREDENTIAL, AUTH, SALT, DSN or WEBHOOK.
- Value patterns such as Stripe (
sk_live_…), GitHub (ghp_…), AWS (AKIA…), Slack, OpenAI and Anthropic keys, JWTs, PEM private keys and URLs with embedded passwords (postgres://user:pass@…). - High-entropy strings — long random-looking values are treated as secrets even if the key name looks harmless.
Safe defaults (ports, log levels, NODE_ENV, booleans, localhost URLs) are kept so the example works out of the box. Check the finished file with the .env file validator, and keep .env out of Git with the .gitignore generator.
Também pesquisado como: .env.example, generate env example, env template, dotenv example, remove secrets from env, find environment variables in code.
Ferramentas que combinam com: .env.example Generator
- Dockerfile Generator — Choose your stack and get a production-ready Dockerfile: multi-stage build, cached dependency layer, non-root user, health check and a matching .dockerignore — explained line by line.
- Gerador do Docker Compose — Marque os serviços que você precisa — aplicativo, banco de dados, cache, interface de administração, captador de e-mails — e receba um arquivo `compose.yaml` limpo com imagens fixadas, volumes nomeados, verificações de integridade e depends_on condições, além de um arquivo .env correspondente com senhas geradas.
- GitHub Actions Workflow Validator — Paste a workflow from .github/workflows and find problems before CI does — invalid triggers, missing runs-on, broken needs, bad expressions, outdated actions and script-injection risks.
- YAML Validator — Paste a Docker Compose file, Kubernetes manifest, GitHub Actions workflow or any YAML to pinpoint errors, catch common pitfalls and get a cleanly formatted version.
Perguntas frequentes
Is my .env file uploaded?
No. Everything runs in your browser. Still, if a real production secret was ever committed or shared, rotate it.
Which languages does code scanning support?
JavaScript and TypeScript (
process.env.X, process.env["X"], import.meta.env.X, Deno.env.get), Python (os.environ, os.getenv), Go (os.Getenv), Ruby (ENV["X"]), PHP (getenv, $_ENV), Rust (env::var), Java (System.getenv), C# and Docker Compose ${VAR} references.What are the type hints?
Short comments such as
# number, # boolean or # url derived from the original value, so whoever fills in the file knows what format is expected.Posso instalar o .env.example Generator como um aplicativo da web e usá-lo offline?
Sim. O .env.example Generator é um aplicativo da web instalável (PWA) — instalado a partir do seu navegador, não baixado de uma loja de aplicativos. Clique em “Instalar aplicativo” na parte superior desta página no Chrome ou no Edge (Windows, macOS, Linux, ChromeOS) ou, no Android, use “Compartilhar” → “Adicionar à tela inicial” no iPhone e no iPad, ou “Arquivo” → “Adicionar ao Dock” no Safari 17+ em um Mac. Em seguida, ela se abre em uma janela própria com seu próprio ícone e, como é executada inteiramente no seu navegador, continua funcionando offline. O Firefox no desktop não permite a instalação de aplicativos da web. Como funciona a instalação.