Skip to content

docs(env-example): add NODE_ENV — used by env.js's production hard-fail#220

Merged
CryptoJones merged 1 commit into
masterfrom
docs/env-example-add-node-env
May 19, 2026
Merged

docs(env-example): add NODE_ENV — used by env.js's production hard-fail#220
CryptoJones merged 1 commit into
masterfrom
docs/env-example-add-node-env

Conversation

@CryptoJones
Copy link
Copy Markdown
Owner

Closes #219.

Summary

.env.example was missing NODE_ENV despite env.js reading it to gate the empty-DB_PASSWORD hard-fail. README env table already covers it (#176); this brings the example file into sync.

Test plan

  • npm run lint clean
  • npm test — 669 passed (docs-only)

Proudly Made in Nebraska. Go Big Red! 🌽 https://xkcd.com/2347/

… env.js, never documented

`.env.example` was missing `NODE_ENV` despite the code consuming it
in `app/config/env.js` to gate the empty-DB_PASSWORD hard-fail.
Operators reading the example file as the canonical reference (per
its own header) missed one of the 19 env vars the app actually
reads.

The README env table already covers NODE_ENV after #176. This
brings `.env.example` into sync with both the README and the actual
code.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@CryptoJones CryptoJones merged commit a649b30 into master May 19, 2026
3 checks passed
@CryptoJones CryptoJones deleted the docs/env-example-add-node-env branch May 19, 2026 10:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

.env.example missing NODE_ENV — env.js reads it for the production hard-fail

1 participant