Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
CryptoJones merged 1 commit into from
May 19, 2026
Merged

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions .env.example
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down