Skip to content

Commit 0f56343

Browse files
authored
Enhance README with Telegram bot and DB settings
Added detailed settings for Telegram bot and optional MySQL database configuration.
1 parent 56d60a0 commit 0f56343

1 file changed

Lines changed: 18 additions & 4 deletions

File tree

README.md

Lines changed: 18 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -72,10 +72,24 @@ Copy `.env.example` to `.env` and fill in:
7272
cp .env.example .env
7373
```
7474

75-
- `API_ID`
76-
- `API_HASH`
77-
- `BOT_TOKEN`
78-
- `ADMIN_ID`
75+
**Telegram Bot Settings:**
76+
77+
- `API_ID` – Your API ID from [my.telegram.org](https://my.telegram.org)
78+
- `API_HASH` – Your API hash from [my.telegram.org](https://my.telegram.org)
79+
- `BOT_TOKEN` – Your bot token from [@BotFather](https://t.me/BotFather)
80+
- `ADMIN` – Your username or user ID. Multiple admins supported, comma-separated (e.g., `1234,12345`)
81+
- `BOT_NAME` – Your bot's name (default: `GetAnyMessage`)
82+
83+
**Database Settings (Optional, for MySQL session storage):**
84+
85+
- `DB_FLAG` – Enable MySQL session storage (`yes`) or disable (`no` / leave empty)
86+
- `DB_HOST` – MySQL host (default: `localhost`)
87+
- `DB_PORT` – MySQL port (default: `3306`)
88+
- `DB_USER` – MySQL username
89+
- `DB_PASS` – MySQL password
90+
- `DB_NAME` – MySQL database name
91+
92+
> ⚠️ If `DB_FLAG` is `no` or empty, all DB_* variables are ignored and the bot will use file-based session storage.
7993
8094
---
8195

0 commit comments

Comments
 (0)