Local Telegram Bot API + streaming chunked transfers #49

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Open

amarabass3435 wants to merge 2 commits into Dominux:main from amarabass3435:feat/local-telegram-bot-api-streaming

amarabass3435 commented Jan 13, 2026

What was added

Added optional support for running Telegram’s Local Bot API server (telegram-bot-api in --local mode) alongside Pentaract via Docker Compose.
Added disk-backed streaming for uploads and downloads so large files don’t need to be buffered fully in RAM.
Added configurable chunk sizing (up to ~2GB per chunk when Local Bot API is enabled) to support very large files by splitting them into Telegram document chunks.

Why

The official Telegram Bot API has practical size limits that make large uploads/downloads unreliable.
Local Bot API allows much larger payloads, and streaming avoids high memory usage during transfers.

How to use

Create/adjust your .env:

TELEGRAM_LOCAL_API=true
TELEGRAM_API_BASE_URL=http://telegram-bot-api:8081
TELEGRAM_API_ID=... and TELEGRAM_API_HASH=... (Telegram app credentials. Create one here)
TELEGRAM_CHUNK_SIZE_MB=1950 (safe default under the ~2GB limit)
WORK_DIR=/work

Start everything:

docker compose up -d --build

Upload/download normally through the API/UI:

Files are automatically chunked (if needed) and streamed during upload/download.

Linares and others added 2 commits

January 9, 2026 21:51


          fix docker and no displaying empty storages

d1448f3


          feat: local telegram-bot-api + streaming chunked transfers

5776d45

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet