.env.telegram.example

# VibraVid TGBot — Telegram bot credentials (the "telegram" service).
# Copy this file to .env.telegram and fill it in:
#   cp .env.telegram.example .env.telegram
# Kept intentionally separate from the main .env (docker-compose.yml): the
# bot's credentials NEVER go through Conf/login.json or Conf/config.json.
#
# The telegram service NEVER sends files over Telegram: it searches, starts
# downloads on VibraVid, and reports status as text only. See
# .github/MkDoc/docs/en/telegram.md (or docs/it/ for Italian).

# ── Credentials (required) ──────────────────────────────────────────────────

# Bot token, from @BotFather on Telegram.
TG_BOT_TOKEN=

# api_id / api_hash for the Telethon application, free from
# https://my.telegram.org ("API development tools" section).
TG_API_ID=
TG_API_HASH=

# ── Access ───────────────────────────────────────────────────────────────────

# Numeric Telegram IDs allowed to use the bot, comma-separated
# (e.g. 123456789,987654321). Empty = anyone who writes to the bot can use
# it: setting this is recommended. To find your own ID, just message a bot
# like @userinfobot.
TG_BOT_TOKEN=
TG_API_ID=
TG_API_HASH=
TG_ALLOWED_USERS=

# ── Network ──────────────────────────────────────────────────────────────────

# Internal URL of the VibraVid GUI, used by the bot for search/start/status
# of downloads. The default works as-is on the internal docker-compose
# network (the "vibravid" service name); no need to change it unless you
# have a non-standard topology.
# TG_GUI_URL=http://vibravid:8000

# Optional shared secret: if set, every request from the bot to the GUI
# includes the X-VibraVid-Token header with this value, and the GUI rejects
# calls without a matching token. Must be set to the SAME value in the
# "vibravid" service's environment too (not in this file).
# VIBRAVID_BOT_SECRET=