From b7e02dd9c8c32b61c0ef120fb9f612d0a5c4551e Mon Sep 17 00:00:00 2001 From: anonsaber Date: Sat, 10 Oct 2026 19:27:20 +0800 Subject: [PATCH] docs: update cron-drain example to use MW_APP_DOMAIN parameter (auto-prepend https://) --- README.md | 4 ++-- README.zh-CN.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 80e59f0..b2d46f1 100644 --- a/README.md +++ b/README.md @@ -256,10 +256,10 @@ Push delivery can be delayed or missed; an external scheduler is the safety net. that can reach your origin, every 5–10 minutes: ```sh -MW_APP_URL=https://mw.example.com \ +MW_APP_DOMAIN=mw.example.com \ MW_WORKER_TOKEN= \ MW_RECONCILE_TOKEN= \ -scripts/cron-drain.sh +scripts/cron-drain.sh --once ``` The script drains the queue (`/worker`) and rescans for missed pushes (`/reconcile`); both return diff --git a/README.zh-CN.md b/README.zh-CN.md index 5708254..a11d9da 100644 --- a/README.zh-CN.md +++ b/README.zh-CN.md @@ -175,10 +175,10 @@ curl -s "https://api.telegram.org/bot/getWebhookInfo" Push 投递可能延迟或丢失；外部调度器是兜底。在任意一台能访问你源站的机器上，每 5–10 分钟跑一次： ```sh -MW_APP_URL=https://mw.example.com \ +MW_APP_DOMAIN=mw.example.com \ MW_WORKER_TOKEN= \ MW_RECONCILE_TOKEN= \ -scripts/cron-drain.sh +scripts/cron-drain.sh --once ``` 脚本会排空队列（`/worker`）并重扫漏掉的 push（`/reconcile`）；两者成功都回答 204 空 body。`MW_RECONCILE_TOKEN` 是可选的——省略时跳过 reconcile 步骤，只排空队列。如果你把负载均衡器放在前面，`/worker` 必须直达后端源站——原因见 §6.3。