Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs(env): set NODE_EXTRA_CA_CERTS at launch, not in .env

Yudhi Armyndharis7e8014a1631f
diff --git a/.env.example b/.env.example
index b585777de..253e25f39 100644
--- a/.env.example
+++ b/.env.example
@@ -385,7 +385,10 @@ DATABASE_SYNCHRONIZE=false # WARNING: Set false in production! (data DB
# REDIS_USERNAME=
# REDIS_PASSWORD=
# Connect to Redis over TLS (a managed Redis that requires it). Uses Node's default CA store; add a
-# private CA with NODE_EXTRA_CA_CERTS. Not for the built-in Redis container, which serves plain TCP.
+# private CA with NODE_EXTRA_CA_CERTS=/path/ca.pem in the environment that launches node (shell, systemd
+# unit, or a compose environment: entry plus a read-only mount of the CA file). Node reads it only at
+# launch, so a value in this file has no effect. Not for the built-in Redis container, which serves
+# plain TCP.
# REDIS_TLS=false
# Redis logical database for the cache (the queue uses the default database).
# REDIS_CACHE_DB=1