docs/hermes_infra-telegram-mapping
This branch is 14 commits behind admin/ansible:master
The prod hermes-gateway (stack=hermes_infra, chat-id=-1004417969359) and a separate poc gateway (stack=hermes, chat-id=-1004355191149) share the same service name in two compose files. Anyone editing hermes_infra/stack-compose.yml without seeing the poc compose risks scaling the wrong stack or merging the two into one compose — which would double-respond to inbound Telegram messages and make 'interrupted by user message' warnings meaningless. This change replaces the stale squid/blackboard README with a terse one (what / how to update / pitfall) and adds a sibling doc that records the current chat-id ↔ service mapping. Future changes must keep that table consistent. Refs admin/ansible#26.
Description
No description provided
12 MiB
Languages
Jinja
43.6%
Python
43.3%
Shell
9.7%
Dockerfile
3.4%