.env.example

# Copy this file to `.env` and fill in real values. `.env` is git-ignored.

# --- Telegram ---------------------------------------------------------------
# Token from @BotFather
BOT_TOKEN=123456:ABC-your-token-here

# Telegram user ID of the owner. Always an admin, can never be demoted.
OWNER_ID=521715249

# --- Proxy ------------------------------------------------------------------
# Used for every call to api.telegram.org. Leave empty for a direct connection.
# A "mixed" inbound (v2rayN / Xray / Clash) accepts both schemes on one port:
#   socks5://127.0.0.1:10808   <- recommended
#   http://127.0.0.1:10808
# Use socks5h:// if you want DNS resolved by the proxy instead of locally.
PROXY_URL=socks5://127.0.0.1:10808

# Used only by docker-compose, which ignores PROXY_URL on purpose: inside a
# container 127.0.0.1 is the container itself, so a host proxy is unreachable
# there. Leave this unset in deployment — a server needs no proxy.
#DOCKER_PROXY_URL=socks5://host.docker.internal:10808

# --- Misc -------------------------------------------------------------------
# Directory for persisted state. Relative paths resolve to the project root.
# It holds one database, bot.db (SQLite, WAL mode), with every table in it:
# the admin roster, the link catalog, panel settings, subscribers, per-day
# metrics, and the channels that gate delivery.
#
# Backups: copy bot.db while the bot is stopped. A clean shutdown folds the WAL
# back in, so that single file is complete. To copy it while the bot is running,
# take bot.db, bot.db-wal and bot.db-shm together.
#
# Note: the catalog stores Telegram file_ids, which are only valid for THIS bot
# token. Changing BOT_TOKEN invalidates every saved link, so keep the token and
# the database together when you back up or move the bot.
DATA_DIR=data

# DEBUG | INFO | WARNING | ERROR
LOG_LEVEL=INFO