env.dev

.env Builder

Generate .env templates for Node.js, Docker, and AWS. Review defaults and loader instructions, then copy or download.

Last updated:

Downloaded filenames are suggestions. Node.js needs an explicit --env-file path or configured dotenv loader. Docker Compose uses .env for interpolation; container variables need environment or env_file. AWS SDKs read the process environment, not this file. Selecting production does not make .env.production load automatically. Fill blank values only when your application requires them and review defaults before deployment.

.env.development
# --- Runtime ---
NODE_ENV=development
PORT=3000
LOG_LEVEL=debug
NODE_OPTIONS=--enable-source-maps

# --- Database ---
# ⚠ sensitive
DATABASE_URL=postgres://localhost:5432/myapp_dev

# --- Cache ---
REDIS_URL=redis://localhost:6379

# --- API ---
# ⚠ sensitive
API_KEY=

How to Use .env Builder

  1. 1Pick a template that matches your stack (Node.js, Docker, AWS).
  2. 2Choose the target environment: development, staging, or production.
  3. 3Copy the generated .env file to your clipboard, or download it directly.
  4. 4Fill in any values left blank — the generator marks sensitive variables that you must supply yourself.

Frequently Asked Questions

Is anything sent to a server?

No. The .env builder runs entirely in your browser. Templates and defaults are bundled with the page. Completion analytics contain only the tool slug and action, never file contents.

Can I add my own template?

Not from the UI today. The templates are defined in the source — open a PR if you want to add or refine one.