food-market/deploy/telegram-bridge/requirements.txt at 3fd2f8a2233dd68898afb5e0fb791bb608bd5ec1 - nns/food-market - food-market git

nns/food-market

nurdotnet d455087bc8 feat(ops): Telegram <-> tmux bridge + local docker-registry unit

Telegram bridge lets me drive the local Claude Code tmux session from my
phone — inbound messages are typed into the 'claude' session, pane diffs
are streamed back as plain Telegram messages (TUI noise, tool-call
blocks, echoed user input and already-sent lines are filtered so only
the assistant's actual reply reaches the chat). Deployed as
food-market-telegram-bridge.service, reads creds from
/etc/food-market/telegram.env (not committed).

Also committing the local docker-registry unit for reproducibility —
registry:2 on 127.0.0.1:5001, data persisted in
/opt/food-market-data/docker-registry.

Setup docs in docs/telegram-bridge.md.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-04-23 10:53:45 +05:00

2 lines

40 B

Plaintext

Raw Blame History

python-telegram-bot[rate-limiter]==21.6