Added
BOT_LABEL — multi-bot-friendly notification prefix
Optional env var / Web UI field (max 32 chars). When set, every outgoing notification gets the label prepended so multiple Docksentry instances sharing a chat / channel can be told apart:
🖥 pve1 · 🔄 Auto Self-Update / 🗓️ New: ... | Old: ...
🖥 pve2 · 🔄 Auto Self-Update / 🗓️ New: ... | Old: ...
🖥 pve3 · 🔄 Auto Self-Update / 🗓️ New: ... | Old: ...
Applied across all three channels:
| Channel | Where the label appears |
|---|---|
| Telegram | Prepended to the message text: 🖥 pve1 · …
|
| Discord | Added to embed title + footer (Docksentry · pve1)
|
| Generic webhook | New top-level bot_label field in the JSON payload
|
Empty (default) keeps single-host behaviour unchanged.
README: "Multi-bot setup (one group, multiple hosts)" section
Step-by-step for running one Docksentry per Docker host into a single Telegram group, with BOT_LABEL for identification. Includes:
- Compose snippets for two hosts
@BotFather → /setprivacy → Disablereminder- Security checklist:
TELEGRAM_ALLOWED_USERSlock-down required, privacy-mode implications, group-trust caveat - Note that Telegram's own bot-to-bot filter rules out loop attacks
This is a stepping stone — not a replacement for the v2.0 multi-host refactor (you still maintain N bots, N containers). But it makes "one chat, all hosts" usable today.
docker pull amayer1983/docksentry:latest
docker compose up -d