From 9581d28b11d24c69647eb3a96ff9a7733ec7ee54 Mon Sep 17 00:00:00 2001 From: "Aaron K. Clark" Date: Tue, 19 May 2026 05:53:35 -0500 Subject: [PATCH] =?UTF-8?q?docs(env-example):=20add=20NODE=5FENV=20?= =?UTF-8?q?=E2=80=94=20used=20by=20the=20production=20hard-fail=20in=20env?= =?UTF-8?q?.js,=20never=20documented?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit `.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) --- .env.example | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/.env.example b/.env.example index c96d7f7..4ce5c49 100644 --- a/.env.example +++ b/.env.example @@ -6,6 +6,15 @@ # # `.env` is gitignored; this `.env.example` file is the canonical reference. +# ---- Mode ---- + +# Set to `production` to enable strict startup checks (most importantly: +# the server refuses to boot when DB_PASSWORD is empty instead of warning +# and continuing). Leave unset / `development` for local + test runs that +# don't need a real database. The Dockerfile and docker-compose.yml api +# service both default this to `production` automatically. +# NODE_ENV=production + # ---- HTTP server ---- # Port the API listens on. Use a non-privileged port (>1024) so the process