.env.example

# =============================================================================
# LeechBot Environment Configuration
# =============================================================================
# Copy this file to .env and fill in your values.
# All settings have sensible defaults — only API_ID, API_HASH, BOT_TOKEN,
# OWNER_ID, and DUMP_ID are required.
# =============================================================================

# --- Telegram Credentials (REQUIRED) ---
API_ID=12345
API_HASH=your_api_hash_here
BOT_TOKEN=your_bot_token_here
OWNER_ID=123456789
DUMP_ID=-1001234567890

# --- Paths ---
# Base directory for all bot working files (downloads, temp, thumbnails, etc.)
# Default: /tmp/leechbot
LEECHBOT_BASE_DIR=/tmp/leechbot

# --- Download Settings ---
# Auto-retry failed downloads N times (default: 3)
AUTO_RETRY_COUNT=3

# Default upload mode: "media" (streaming) or "document"
DEFAULT_UPLOAD_MODE=media

# Bandwidth limit for aria2c downloads (empty = unlimited)
# Examples: "10M" (10 MB/s), "500K" (500 KB/s), "1G" (1 GB/s)
BANDWIDTH_LIMIT=

# --- Web Dashboard ---
# Port for the web dashboard (default: 8080)
WEB_PORT=8080
# Auth token for web dashboard (auto-generated if empty)
WEB_TOKEN=

# --- Google Drive ---

# Path to token.pickle file for Google Drive API
# Default: <BASE_DIR>/token.pickle
TOKEN_PICKLE_PATH=

# --- Multi-User Support ---
# Comma-separated list of Telegram user IDs allowed to use the bot
# The OWNER_ID is always allowed; this is for additional users
# Example: ALLOWED_USERS=123456789,987654321
ALLOWED_USERS=

# --- YT-DLP Cookie Authentication (fixes YouTube bot detection) ---
# Option 1: Path to a Netscape-format cookies.txt file
#   Export cookies from your browser using a cookies editor extension.
#   See: https://github.com/yt-dlp/yt-dlp/wiki/FAQ#how-do-i-pass-cookies-to-yt-dlp
# YTDL_COOKIES_FILE=/path/to/cookies.txt