mirror of
https://github.com/dreamhunter2333/cloudflare_temp_email.git
synced 2026-09-04 23:17:34 +08:00
feat: add daily request limit and refactor access control (#759)
- Add daily request limit per IP in blacklist settings (1-1,000,000/day) - Refactor access control logic: merge blacklist and rate limit checks - Remove RATE_LIMIT_API_DAILY_REQUESTS env var, use database config instead - Move x-custom-auth check earlier in middleware chain - Add comprehensive English documentation (31 new guide pages) - Improve code structure and error handling 🤖 Generated with [Claude Code](https://claude.ai/code) Co-authored-by: Claude <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,66 @@
|
||||
# Configure Telegram Bot
|
||||
|
||||
Try it here: [@cf_temp_mail_bot](https://t.me/cf_temp_mail_bot)
|
||||
|
||||
::: warning Note
|
||||
The default `worker.dev` domain certificate for worker is not supported by Telegram. Please use a custom domain when configuring Telegram Bot.
|
||||
:::
|
||||
|
||||
> [!NOTE]
|
||||
> If you want to use Telegram Bot, please bind `KV` first
|
||||
>
|
||||
> If you don't need Telegram Bot, you can skip this step
|
||||
>
|
||||
> If you want Telegram to have stronger email parsing capabilities, refer to [Configure worker to use wasm for email parsing](/en/guide/feature/mail_parser_wasm_worker)
|
||||
|
||||
## Telegram Bot Configuration
|
||||
|
||||
Please first create a Telegram Bot, obtain the `token`, then execute the following command to add the `token` to secrets
|
||||
|
||||
> [!NOTE]
|
||||
> If you find it troublesome, you can also put it in plain text under `[vars]` in `wrangler.toml`, but this is not recommended
|
||||
|
||||
If you deployed via UI, you can add it under `Variables and Secrets` in the Cloudflare UI interface
|
||||
|
||||
```bash
|
||||
# Switch to worker directory
|
||||
cd worker
|
||||
pnpm wrangler secret put TELEGRAM_BOT_TOKEN
|
||||
```
|
||||
|
||||
## Bot
|
||||
|
||||
- Can set whitelist users
|
||||
- Click `Initialize` to complete the configuration.
|
||||
- Click `View Status` to check the current configuration status.
|
||||
|
||||

|
||||
|
||||
## Mini App
|
||||
|
||||
Can be deployed via command line or UI interface
|
||||
|
||||
### UI Deployment
|
||||
|
||||
For other steps, refer to `Frontend and Backend Separation Deployment` in [UI Deployment](/en/guide/cli/pages)
|
||||
|
||||
> [!NOTE]
|
||||
> Download the zip from here, [telegram-frontend.zip](https://github.com/dreamhunter2333/cloudflare_temp_email/releases/latest/download/telegram-frontend.zip)
|
||||
>
|
||||
> Modify the index-xxx.js file in the zip, where xx is a random string
|
||||
>
|
||||
> Search for `https://temp-email-api.xxx.xxx`, replace it with your worker domain, then deploy the new zip file
|
||||
|
||||
### Command Line Deployment
|
||||
|
||||
```bash
|
||||
cd frontend
|
||||
pnpm install
|
||||
cp .env.example .env.prod
|
||||
# --project-name can create a separate pages for mini app, you can also share one pages, but may encounter js loading issues
|
||||
pnpm run deploy:telegram --project-name=<your_project_name>
|
||||
```
|
||||
|
||||
- After deployment, please fill in the web URL in the `Settings` -> `Telegram Mini App` page `Telegram Mini App URL` in the admin backend.
|
||||
- Please execute `/setmenubutton` in `@BotFather`, then enter your web address to set the `Open App` button in the lower left corner.
|
||||
- Please execute `/newapp` in `@BotFather` to create a new app and register the mini app.
|
||||
Reference in New Issue
Block a user