Fixed
/history now records Docksentry's own self-updates
Closes #13. Previously /history and the Web UI history page only showed regular container updates — Docksentry's own self-updates were invisible because the history-write code was wired from the container-update path but never from the selfupdate path. Now a history entry is written just before the helper container restarts the bot, so the event survives the process death.
In /history and the Web UI:
✅ docksentry — 2026-05-30 21:31:44
🗓️ 2026-05-29 → 2026-05-30 (selfupdate)
Useful when a Docksentry upgrade coincides with a container starting to misbehave — you can now correlate.
Docs
README "Group / Topic setup" — Group ≠ Channel warning
The most common cause of "bot posts startup message but doesn't respond to /commands" is creating a Telegram Channel (broadcast-only — no incoming messages) instead of a Group. The README's "Group / Topic setup" section now starts with a prominent warning calling this out explicitly.
/setprivacy cache caveat
Also added: toggling /setprivacy → Disable in BotFather after the bot has already joined the group doesn't apply retroactively. docker compose down/up of Docksentry does not help. The bot has to be kicked from the group and re-added for the new privacy setting to take effect.
Both based on @famewolf's first-time-setup feedback.
docker pull amayer1983/docksentry:latest
docker compose up -d