everythingsuckz/tg-filestreambot

Purpose and Runtime

TG-FileStreamBot is a Go service that turns Telegram-hosted files into direct HTTP streaming/download links. It combines a Telegram bot interface with an HTTP server and a Telegram user-session client used to retrieve file bytes.

Primary executable: cmd/fsb/main.go. Process startup, bot/session initialization, and service orchestration are organized in cmd/fsb/run.go and cmd/fsb/session.go.

Bootstrap and Configuration

cmd/fsb/main.go launches the application; cmd/fsb/run.go composes the major subsystems. config/config.go is the central configuration boundary, likely sourcing bot credentials, Telegram API/session settings, server configuration, and cache behavior from environment variables.

Deployment targets include containerized and process-platform environments via Dockerfile, docker-compose.yaml, and Procfile.

Telegram Interaction Layer

The Telegram-facing application is implemented in internal/bot/userbot.go, internal/bot/client.go, and internal/bot/middleware.go. This layer owns Telegram client connectivity, incoming update handling, and cross-cutting bot validation/error behavior.

Command dispatch lives in internal/commands/commands.go. User-facing workflows include startup/onboarding in internal/commands/start.go and generation of stream links from Telegram messages/files in internal/commands/stream.go.

File-Link and Response Flow

A user submits or references a Telegram file through the bot. The command layer resolves file metadata and produces a stream-link response using shared models in internal/types/file.go and internal/types/response.go.

Link generation and file-access identity depend on utility functions such as hashing in internal/utils/hashing.go. This separates externally exposed stream identifiers from Telegram’s underlying file references.

HTTP Routing and Stream Delivery

The public HTTP boundary is defined by internal/routes/routes.go, with stream-specific endpoint handling in internal/routes/stream.go. These handlers accept a generated link/request, resolve the corresponding Telegram file, and return an HTTP response suitable for browser/media-client consumption.

Actual transfer is handled by internal/stream/pipe.go; stream failures are modeled in internal/stream/errors.go. This is the key protocol boundary: HTTP request/response semantics on one side, Telegram file retrieval on the other.

Session, Caching, and Background Work

Telegram user authorization/session lifecycle is coordinated from cmd/fsb/session.go; QR-login support is packaged in pkg/qrlogin/qrcode.go and pkg/qrlogin/encoder.go. This supports authenticated Telegram file access independently of the bot command channel.

internal/cache/cache.go provides a state/cache boundary for reusable file or link-related data. internal/bot/workers.go contains asynchronous/background bot work, keeping long-running or deferred tasks outside the immediate update handler path.

External Dependencies and Operational Boundaries

The system integrates with Telegram through bot and user-client APIs, including the credited gotgproto ecosystem. Telegram is the authoritative file source; the service exposes the derived HTTP streaming surface. Runtime observability/logging utilities are centralized in internal/utils/logger.go, while releases are built and packaged through .goreleaser.yaml and GitHub release automation.