commit ebadce7ef7165b6438433798168dccde1e12bbe5
parent b7f8e845b8ac11f8c0e0972b7bcb253f6df05d8d
Author: notamitgamer-bot <bot@users.noreply.github.com>
Date: Sat, 29 Aug 2026 02:17:10 +0000
deploy-backend docs: document EXCLUDED_JIDS config for skipping chats from logging
Mirrors the same section added to the project README, showing where
to edit src/config.js to exclude specific JIDs (bots, broadcast/
status, business accounts, etc.) from being cached, streamed, or
exported entirely.
Diffstat:
1 file changed, 27 insertions(+), 0 deletions(-)
diff --git a/src/whatsapp-logger/deploy-backend.md b/src/whatsapp-logger/deploy-backend.md
@@ -25,4 +25,31 @@ order: 870
Go to `https://your-app.onrender.com/logs` to see the logs from server. You have to login first to see the logs.
!!!
+## Excluding specific chats from logging
+
+If there are chats you don't want logged at all — a bot, a broadcast/status JID, a business account — edit `EXCLUDED_JIDS` in `src/config.js` on your fork before deploying:
+
+```javascript
+// --- CONFIGURATION ---
+const PORT = process.env.PORT || 3000;
+const AUTH_USER = process.env.AUTH_USER;
+const AUTH_PASS = process.env.AUTH_PASS;
+const MAX_LOGS = 500;
+const MAX_CONNECTIONS_PER_TOKEN = 15;
+const VERSION = '4.2.3';
+const EXCLUDED_JIDS = new Set(['']);
+
+module.exports = {
+ PORT,
+ AUTH_USER,
+ AUTH_PASS,
+ MAX_LOGS,
+ MAX_CONNECTIONS_PER_TOKEN,
+ VERSION,
+ EXCLUDED_JIDS
+};
+```
+
+`EXCLUDED_JIDS` is a set of full JIDs (the `...@s.whatsapp.net` / `...@g.us` / `...@lid` identifiers, not just a phone number) that are skipped entirely — they won't be cached, streamed, or included in exports. It ships empty by default. You can find a chat's exact JID from the live server logs (see the tip above) the first time it logs a message, then add it here, e.g. `new Set(['917278779512@s.whatsapp.net', '201554426618024@lid'])`, and redeploy.
+
Continue to [Connect WhatsApp](connect-whatsapp.md).
