Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs(devops): stop pinning a Chromium path in the env excerpt

Yudhi Armyndharis8074de7f0ec1
diff --git a/docs/10-devops-infrastructure.md b/docs/10-devops-infrastructure.md
index 8dcf64cb4..b97556c6f 100644
--- a/docs/10-devops-infrastructure.md
+++ b/docs/10-devops-infrastructure.md
@@ -442,7 +442,8 @@ LOG_FORMAT=json
# SESSION_DATA_PATH=./data/sessions
# Puppeteer (for whatsapp-web.js)
-PUPPETEER_EXECUTABLE_PATH=/usr/bin/chromium
+# Path to a system Chromium/Chrome binary. Leave unset to use the bundled browser; the Docker image sets its own.
+# PUPPETEER_EXECUTABLE_PATH=/usr/bin/chromium
# PUPPETEER_HEADLESS=true
# PUPPETEER_ARGS=--no-sandbox,--disable-setuid-sandbox,--disable-dev-shm-usage,--disable-gpu
# Optional per-browser-command budget, ms. Unset = Puppeteer's own budget. Raise only after seeing