⭐AI-driven public opinion & trend monitor with multi-platform aggregation, RSS, and smart alerts.🎯 告别信息过载,你的 AI 舆情监控助手与热点筛选工具!聚合多平台热点 + RSS 订阅,支持关键词精准筛选。AI 智能筛选新闻 + AI 翻译 + AI 分析简报直推手机,也支持接入 MCP 架构,赋能 AI 自然语言对话分析、情感洞察与趋势预测等。支持 Docker ,数据本地/云端自持。集成微信/飞书/钉钉/Telegram/邮件/ntfy/bark/slack 等渠道智能推送。
Python aibarkdata-analysisdockerhot-newsllmmailmcpmcp-servernewsntfypythonrsstrending-topicswechatwework
docs: 优化文档
sansan8849d165e815
diff --git a/README-EN.md b/README-EN.mdindex 12ebe7bcc9..0b857a875e 100644--- a/README-EN.md+++ b/README-EN.md@@ -8,6 +8,8 @@<a href="https://trendshift.io/repositories/14726" target="_blank"><img src="https://trendshift.io/api/badge/repositories/14726" alt="sansan0%2FTrendRadar | Trendshift" style="width: 250px; height: 55px;" width="250" height="55"/></a>+<a href="https://shandianshuo.cn" target="_blank" title="AI Voice Input, 4x Faster Than Typing ⚡"><img src="_image/shandianshuo.png" alt="FlashSpeak logo" height="50"/></a>+[](https://github.com/sansan0/TrendRadar/stargazers)[](https://github.com/sansan0/TrendRadar/network/members)[](LICENSE)@@ -115,6 +117,16 @@ After communication, the author indicated no concerns about server pressure, but## 🪄 Sponsors+> Writing reports, replying messages making your wrists tired? Try「FlashSpeak」AI Voice Input - Speak instead of type, 4x faster ⚡++<div align="center">++[](https://shandianshuo.cn) [](https://shandianshuo.cn)+<a href="https://shandianshuo.cn" target="_blank">+ <img src="_image/banner-shandianshuo.png" alt="FlashSpeak" width="700"/>+</a>+</div>+<br>## 📝 Changelog@@ -814,9 +826,9 @@ Transform from "algorithm recommendation captivity" to "actively getting the inf## 🚀 Quick Start-> **📖 Reminder**: You should first **[check the latest official documentation](https://github.com/sansan0/TrendRadar?tab=readme-ov-file)** to ensure the configuration steps are up to date.+> **Reminder**: You should first **[check the latest official documentation](https://github.com/sansan0/TrendRadar?tab=readme-ov-file)** to ensure the configuration steps are up to date.-### 🛠️ Choose the Deployment Method That Fits You+### Choose the Deployment Method That Fits You#### 🅰️ Option A: Docker Deployment (Recommended 🔥)@@ -839,6 +851,8 @@ Transform from "algorithm recommendation captivity" to "actively getting the inf> - Any mention of "Fork" in this document can be understood as "Use this template"> - Using Fork may cause runtime issues, see [Issue #606](https://github.com/sansan0/TrendRadar/issues/606)+ <br>+2️⃣ **Setup GitHub Secrets**:In your forked repo, go to `Settings` > `Secrets and variables` > `Actions` > `New repository secret`@@ -850,55 +864,13 @@ Transform from "algorithm recommendation captivity" to "actively getting the inf- **DO NOT Create Custom Names**: The Secret Name must **strictly use** the names listed below (e.g., `WEWORK_WEBHOOK_URL`, `FEISHU_WEBHOOK_URL`, etc.). Do not modify or create new names arbitrarily, or the system will not recognize them- **Can Configure Multiple Platforms**: The system will send notifications to all configured platforms- **GitHub Actions Check-In Renewal Mechanism**:- - **Running Cycle**: Valid for **7 days**—service will automatically suspend when countdown ends.- - **Renewal Method**: Manually trigger the "Check In" workflow on the Actions page to reset the 7-day validity period.- - **Operation Path**: `Actions` → `Check In` → `Run workflow`- - **Design Philosophy**:- - If you forget for 7 days, maybe you don't really need it. Letting it stop is a digital detox, freeing you from the constant impact.- - GitHub Actions is a valuable public computing resource. The check-in mechanism aims to prevent wasted computing cycles, ensuring resources are allocated to truly active users who need them. Thank you for your understanding and support.-- <details>- <summary>👉 Click to expand: <strong>Lite Mode vs Full Mode + AI Analysis</strong></summary>- <br>--**Two Deployment Modes:**--| Mode | Configuration Required | Features |-|------|------------------------|----------|-| **Lite Mode** | No storage configuration needed | Real-time crawling + Keyword filtering + Multi-channel push |-| **Full Mode** | Configure remote cloud storage | Lite Mode + New detection + Trend tracking + Incremental push + AI analysis |--**Lite Mode Description**:-- ✅ Available: Real-time news crawling, keyword filtering, hotspot weight ranking, current list push-- ❌ Not Available: New news detection (🆕), trend tracking, incremental mode, daily summary accumulation, MCP AI analysis--**Full Mode Description**:-Configure remote cloud storage to unlock all features (see **Recommended Configuration: Remote Cloud Storage** below)-- </details>-- <details>- <summary>👉 Click to expand: <strong>Multi-Account Push Notes (v3.5.0 New Feature)</strong></summary>- <br>--- **Multi-Account Configuration Support**: All push channels (Feishu, DingTalk, WeWork, Telegram, ntfy, Bark, Slack) support configuring multiple accounts-- **Configuration Method**: Use English semicolon `;` to separate multiple account values-- **Example**: Set `FEISHU_WEBHOOK_URL` Secret value to `https://webhook1;https://webhook2`-- **Paired Configuration**: Telegram and ntfy require paired parameter quantities to match (e.g., token and chat_id both have 2 values)-- **Quantity Limit**: Default maximum 3 accounts per channel, exceeded values will be truncated--**Multi-Account Configuration Examples**:+ **📌 Multi-Account Push Notes (v3.5.0 New Feature):**-| Name | Secret (Value) Example |-|------|------------------------|-| `FEISHU_WEBHOOK_URL` | `https://webhook1;https://webhook2;https://webhook3` |-| `TELEGRAM_BOT_TOKEN` | `token1;token2` |-| `TELEGRAM_CHAT_ID` | `chatid1;chatid2` |-| `NTFY_TOPIC` | `topic1;topic2` |-| `NTFY_TOKEN` | `;token2` (1st has no token, use empty string as placeholder) |-- </details>+ - ✅ **Multi-Account Configuration Support**: All push channels (Feishu, DingTalk, WeWork, Telegram, ntfy, Bark, Slack) support configuring multiple accounts+ - ✅ **Configuration Method**: Use English semicolon `;` to separate multiple account values+ - ✅ **Example**: Set `FEISHU_WEBHOOK_URL` Secret value to `https://webhook1;https://webhook2`+ - ⚠️ **Paired Configuration**: Telegram and ntfy require paired parameter quantities to match (e.g., token and chat_id both have 2 values)+ - ⚠️ **Quantity Limit**: Default maximum 3 accounts per channel, exceeded values will be truncated**Configuration Example:**@@ -910,44 +882,6 @@ Configure remote cloud storage to unlock all features (see **Recommended Configu<br>-<details>-<summary>👉 Click to expand: <strong>Recommended Configuration: Remote Cloud Storage</strong></summary>-<br>--**GitHub Secret Configuration:**--**Required Configuration (4 items):**--| Name | Secret (Value) Description |-|------|----------------------------|-| `S3_BUCKET_NAME` | Bucket name (e.g., `trendradar-data`) |-| `S3_ACCESS_KEY_ID` | Access key ID |-| `S3_SECRET_ACCESS_KEY` | Access key |-| `S3_ENDPOINT_URL` | S3 API endpoint (e.g., R2: `https://<account-id>.r2.cloudflarestorage.com`) |--**Optional Configuration:**--| Name | Secret (Value) Description |-|------|----------------------------|-| `S3_REGION` | Region (default `auto`, some providers may require specification) |--> 💡 **More storage configuration options**: See [Storage Configuration Details](#11-storage-configuration-v400-new)--<br>--**How to Get Credentials (Using Cloudflare R2 as Example):**--1. Visit [Cloudflare Dashboard](https://dash.cloudflare.com/) and log in-2. Select `R2` in left menu → Click `Create Bucket` → Enter name (e.g., `trendradar-data`)-3. Click `Manage R2 API Tokens` at top right → `Create API Token`-4. Select `Object Read & Write` permission → After creation, it will display `Access Key ID` and `Secret Access Key`-5. Endpoint URL can be found in bucket details page (format: `https://<account-id>.r2.cloudflarestorage.com`)--**Notes**:-- Data stored in cloud, keeps GitHub repository clean--</details>-<details><summary> <strong>👉 Click to expand: WeWork Bot</strong> (Simplest and fastest configuration)</summary><br>@@ -1534,6 +1468,7 @@ Slack is a team collaboration tool, Incoming Webhooks can push messages to Slack> - For first deployment, suggest completing **GitHub Secrets** configuration first (choose one push platform), then jump to [Step 3] to test push success.> - **Don't modify** `config/config.yaml` and `frequency_words.txt` temporarily, adjust these configs after push test succeeds as needed.+ <br>3️⃣ **Manual Test News Push**:@@ -1561,6 +1496,8 @@ Slack is a team collaboration tool, Incoming Webhooks can push messages to Slack> - Don't test too frequently to avoid triggering GitHub Actions limits> - After clicking Run workflow, you need to **refresh the browser page** to see the new run record+ <br>+4️⃣ **Configuration Notes (Optional)**:Default configuration works normally. Only adjust if you need personalization, understanding these three files:@@ -1573,7 +1510,84 @@ Slack is a team collaboration tool, Incoming Webhooks can push messages to Slack👉 **Detailed Configuration Tutorial**: [Configuration Guide](#configuration-guide)-5️⃣ **🎉 Deployment Success! Share Your Experience**+ <br>++5️⃣ **GitHub Actions Check-In Mechanism & Remote Cloud Storage Configuration**:++ **v4.0.0 Important Change**: Introduced "Activity Detection" mechanism—GitHub Actions requires periodic check-in to remain active.++ - **Running Cycle**: Valid for **7 days**—service will automatically suspend when countdown ends.+ - **Renewal Method**: Manually trigger the "Check In" workflow on the Actions page to reset the 7-day validity period.+ - **Operation Path**: `Actions` → `Check In` → `Run workflow`+ - **Design Philosophy**:+ - If you forget for 7 days, maybe you don't really need it. Letting it stop is a digital detox, freeing you from the constant impact.+ - GitHub Actions is a valuable public computing resource. The check-in mechanism aims to prevent wasted computing cycles, ensuring resources are allocated to truly active users who need them. Thank you for your understanding and support.++ ---++ **You can also choose NOT to configure remote cloud storage**, but then you will be in **Lite Mode** with some advanced features unavailable.++ **Two Deployment Modes Comparison:**++ | Mode | Configuration Required | Features |+ |------|------------------------|----------|+ | **Lite Mode** | No storage configuration needed | Real-time crawling + Keyword filtering + Multi-channel push |+ | **Full Mode** | Configure remote cloud storage | Lite Mode + New detection + Trend tracking + Incremental push + AI analysis |++ **Lite Mode Description**:+ - ✅ Available: Real-time news crawling, keyword filtering, hotspot weight ranking, current list push+ - ❌ Not Available: New news detection (🆕), trend tracking, incremental mode, daily summary accumulation, MCP AI analysis++ **Full Mode Description**: Configure remote cloud storage to unlock all features. Continue with the configuration below.++ <details>+ <summary>👉 Click to expand: <strong>Remote Cloud Storage Configuration (Determines Feature Completeness) (Optional)</strong></summary>+ <br>++ **⚠️ Prerequisites for Cloudflare R2 Configuration:**++ According to Cloudflare platform rules, enabling R2 requires binding a payment method.++ * **Purpose**: Verify identity only, **no charges will be incurred**.+ * **Payment**: Supports dual-currency credit cards or regional PayPal.+ * **Usage**: R2's free tier (10GB storage/month) is sufficient for this project's daily operation, no need to worry about costs.++ ---++ **GitHub Secret Configuration:**++ **Required Configuration (4 items):**++ | Name | Secret (Value) Description |+ |------|----------------------------|+ | `S3_BUCKET_NAME` | Bucket name (e.g., `trendradar-data`) |+ | `S3_ACCESS_KEY_ID` | Access key ID |+ | `S3_SECRET_ACCESS_KEY` | Access key |+ | `S3_ENDPOINT_URL` | S3 API endpoint (e.g., R2: `https://<account-id>.r2.cloudflarestorage.com`) |++ **Optional Configuration:**++ | Name | Secret (Value) Description |+ |------|----------------------------|+ | `S3_REGION` | Region (default `auto`, some providers may require specification) |++ > 💡 **More storage configuration options**: See [Storage Configuration Details](#11-storage-configuration-v400-new)++ <br>++ **How to Get Credentials (Using Cloudflare R2 as Example):**++ 1. Visit [Cloudflare Dashboard](https://dash.cloudflare.com/) and log in+ 2. Select `R2` in left menu → Click `Create Bucket` → Enter name (e.g., `trendradar-data`)+ 3. Click `Manage R2 API Tokens` at top right → `Create API Token`+ 4. Select `Object Read & Write` permission → After creation, it will display `Access Key ID` and `Secret Access Key`+ 5. Endpoint URL can be found in bucket details page (format: `https://<account-id>.r2.cloudflarestorage.com`)++ </details>++ <br>++6️⃣ **🎉 Deployment Success! Share Your Experience**Congratulations on completing the TrendRadar configuration! You can now start tracking trending news.@@ -1585,7 +1599,9 @@ Slack is a team collaboration tool, Incoming Webhooks can push messages to Slack👉 Follow the WeChat Official Account「**[硅基茶水间](#-faq--support)**」, your likes and comments are the motivation for continuous updates.-6️⃣ **🤖 Want Smarter Analysis? Try AI-Enhanced Features** (Optional)+ <br>++7️⃣ **🤖 Want Smarter Analysis? Try AI-Enhanced Features** (Optional)Basic configuration already meets daily needs, but if you want:diff --git a/README.md b/README.mdindex 9236d82422..ad3da34a6e 100644--- a/README.md+++ b/README.md@@ -8,6 +8,8 @@<a href="https://trendshift.io/repositories/14726" target="_blank"><img src="https://trendshift.io/api/badge/repositories/14726" alt="sansan0%2FTrendRadar | Trendshift" style="width: 250px; height: 55px;" width="250" height="55"/></a>+<a href="https://shandianshuo.cn" target="_blank" title="AI 语音输入,比打字快 4 倍 ⚡"><img src="_image/shandianshuo.png" alt="闪电说 logo" height="50"/></a>+[](https://github.com/sansan0/TrendRadar/stargazers)[](https://github.com/sansan0/TrendRadar/network/members)[](LICENSE)@@ -164,6 +166,16 @@## 🪄 赞助商+> 每天写报告、回复消息是否让手腕疲惫?试试「闪电说」AI 语音输入法 —— 说话,比打字快 4 倍 ⚡++<div align="center">++[](https://shandianshuo.cn) [](https://shandianshuo.cn)+<a href="https://shandianshuo.cn" target="_blank">+ <img src="_image/banner-shandianshuo.png" alt="闪电说" width="700"/>+</a>+</div>+<br>## 📝 更新日志@@ -852,9 +864,9 @@ GitHub 一键 Fork 即可使用,无需编程基础。## 🚀 快速开始-> **📖 提醒**:建议先 **[查看最新官方文档](https://github.com/sansan0/TrendRadar?tab=readme-ov-file)**,确保配置步骤是最新的。+> **提醒**:建议先 **[查看最新官方文档](https://github.com/sansan0/TrendRadar?tab=readme-ov-file)**,确保配置步骤是最新的。-### 🛠️ 请选择适合你的部署方式+### 请选择适合你的部署方式#### 🅰️ 方案一:Docker 部署(推荐 🔥)@@ -877,6 +889,8 @@ GitHub 一键 Fork 即可使用,无需编程基础。> - 后续文档中提到的 "Fork" 均可理解为 "Use this template"> - 使用 Fork 可能导致运行异常,详见 [Issue #606](https://github.com/sansan0/TrendRadar/issues/606)+ <br>+2️⃣ **设置 GitHub Secrets**:在你 Fork 后的仓库中,进入 `Settings` > `Secrets and variables` > `Actions` > `New repository secret`@@ -888,55 +902,23 @@ GitHub 一键 Fork 即可使用,无需编程基础。- **严禁自创名称**:Secret 的 Name(名称)必须**严格使用**下方列出的名称(如 `WEWORK_WEBHOOK_URL`、`FEISHU_WEBHOOK_URL` 等),不能自己随意修改或创造新名称,否则系统无法识别- **可以同时配置多个平台**:系统会向所有配置的平台发送通知- **GitHub Actions 签到续期机制**:- - **运行周期**:有效期为 **7 天**,倒计时结束后服务将自动挂起。- - **续期方式**:在 Actions 页面手动触发 "Check In" workflow,即可重置 7 天有效期。- - **操作路径**:`Actions` → `Check In` → `Run workflow`- - **设计理念**:- - 如果 7 天都忘了签到,或许这些资讯对你来说并非刚需。适时的暂停,能帮你从信息流中抽离,给大脑留出喘息的空间。- - GitHub Actions 是宝贵的公共计算资源。引入签到机制旨在避免算力的无效空转,确保资源能分配给真正活跃且需要的用户。感谢你的理解与支持。-- <details>- <summary>👉 点击展开:<strong>轻量模式 vs 完整模式 + AI分析</strong></summary>- <br>--**两种部署模式:**--| 模式 | 配置要求 | 功能范围 |-|------|---------|---------|-| **轻量模式** | 无需配置存储 | 实时抓取 + 关键词筛选 + 多渠道推送 |-| **完整模式** | 配置远程云存储 | 轻量模式 + 新增检测 + 趋势追踪 + 增量推送 + AI分析 |--**轻量模式说明**:-- ✅ 可用:实时新闻抓取、关键词筛选、热点权重排序、当前榜单推送-- ❌ 不可用:新增新闻检测(🆕)、热度趋势追踪、增量模式、每日汇总累积、MCP AI分析--**完整模式说明**:-配置远程云存储后解锁全部功能(见下方 **推荐配置:远程云存储**)-- </details>-- <details>- <summary>👉 点击展开:<strong>多账号推送说明(v3.5.0 新增)</strong></summary>- <br>+ **📌 多账号推送说明(v3.5.0 新增):**-- **支持多账号配置**:所有推送渠道(飞书、钉钉、企业微信、Telegram、ntfy、Bark、Slack)均支持配置多个账号-- **配置方式**:使用英文分号 `;` 分隔多个账号值-- **示例**:`FEISHU_WEBHOOK_URL` 的 Secret 值填写 `https://webhook1;https://webhook2`-- **配对配置**:Telegram 和 ntfy 需要保证配对参数数量一致(如 token 和 chat_id 都是 2 个)-- **数量限制**:默认每个渠道最多 3 个账号,超出部分被截断+ - **支持多账号配置**:所有推送渠道(飞书、钉钉、企业微信、Telegram、ntfy、Bark、Slack)均支持配置多个账号+ - **配置方式**:使用英文分号 `;` 分隔多个账号值+ - **示例**:`FEISHU_WEBHOOK_URL` 的 Secret 值填写 `https://webhook1;https://webhook2`+ - **配对配置**:Telegram 和 ntfy 需要保证配对参数数量一致(如 token 和 chat_id 都是 2 个)+ - **数量限制**:默认每个渠道最多 3 个账号,超出部分被截断-**多账号配置示例**:+ **多账号配置示例**:-| Name(名称) | Secret(值)示例 |-|-------------|-----------------|-| `FEISHU_WEBHOOK_URL` | `https://webhook1;https://webhook2;https://webhook3` |-| `TELEGRAM_BOT_TOKEN` | `token1;token2` |-| `TELEGRAM_CHAT_ID` | `chatid1;chatid2` |-| `NTFY_TOPIC` | `topic1;topic2` |-| `NTFY_TOKEN` | `;token2`(第一个无 token 时留空占位) |-- </details>+ | Name(名称) | Secret(值)示例 |+ |-------------|-----------------|+ | `FEISHU_WEBHOOK_URL` | `https://webhook1;https://webhook2;https://webhook3` |+ | `TELEGRAM_BOT_TOKEN` | `token1;token2` |+ | `TELEGRAM_CHAT_ID` | `chatid1;chatid2` |+ | `NTFY_TOPIC` | `topic1;topic2` |+ | `NTFY_TOKEN` | `;token2`(第一个无 token 时留空占位) |**配置示例:**@@ -948,65 +930,6 @@ GitHub 一键 Fork 即可使用,无需编程基础。<br>- <details>- <summary>👉 点击展开:<strong>推荐配置:远程云存储</strong></summary>- <br>--**⚠️ 以 Cloudflare R2 为例的配置前置条件:**--根据 Cloudflare 平台规则,开通 R2 需绑定支付方式。--* **目的**:仅作身份验证(Verify Only),**不产生扣费**。-* **支付**:支持双币信用卡或国区 PayPal。-* **用量**:R2 的免费额度(10GB存储/月)足以覆盖本项目日常运行,无需担心付费。-------**GitHub Secret 配置:**--**必需配置(4 项):**--| Name(名称) | Secret(值)说明 |-|-------------|-----------------|-| `S3_BUCKET_NAME` | 存储桶名称(如 `trendradar-data`) |-| `S3_ACCESS_KEY_ID` | 访问密钥 ID(Access Key ID) |-| `S3_SECRET_ACCESS_KEY` | 访问密钥(Secret Access Key) |-| `S3_ENDPOINT_URL` | S3 API 端点(如 R2:`https://<account-id>.r2.cloudflarestorage.com`) |--**可选配置:**--| Name(名称) | Secret(值)说明 |-|-------------|-----------------|-| `S3_REGION` | 区域(默认 `auto`,部分服务商可能需要指定) |--> 💡 **更多存储配置选项**:参见 [存储配置详解](#11-存储配置)--<br>--**如何获取凭据(以 Cloudflare R2 为例):**--1. **进入 R2 概览**:- - 登录 [Cloudflare Dashboard](https://dash.cloudflare.com/)。- - 在左侧侧边栏找到并点击 `R2对象存储`。--2. **创建存储桶**:- - 点击`概述`- - 点击右上角的 `创建存储桶` (Create bucket)。- - 输入名称(例如 `trendradar-data`),点击 `创建存储桶`。--3. **创建 API 令牌**:- - 回到 **概述**页面。- - 点击**右下角** `Account Details `找到并点击 `Manage` (Manage R2 API Tokens)。- - 同时你会看到 `S3 API`:`https://<account-id>.r2.cloudflarestorage.com`(这就是 S3_ENDPOINT_URL)- - 点击 `创建 Account APl 令牌` 。- - **⚠️ 关键设置**:- - **令牌名称**:随意填写(如 `github-action-write`)。- - **权限**:选择 `管理员读和写` 。- - **指定存储桶**:为了安全,建议选择 `仅适用于指定存储桶` 并选中你的桶(如 `trendradar-data`)。- - 点击 `创建 API 令牌`,**立即复制** 显示的 `Access Key ID` 和 `Secret Access Key`(只显示一次!)。-- </details>-<details><summary>👉 点击展开:<strong>企业微信机器人</strong>(配置最简单最迅速)</summary><br>@@ -1589,6 +1512,8 @@ GitHub 一键 Fork 即可使用,无需编程基础。</details>+ <br>+3️⃣ **手动测试新闻推送**:> ⚠️ 提醒:@@ -1616,6 +1541,8 @@ GitHub 一键 Fork 即可使用,无需编程基础。> - 手动测试不要太频繁,避免触发 GitHub Actions 限制> - 点击 Run workflow 后需要刷新浏览器页面才能看到新的运行记录+ <br>+4️⃣ **配置说明(可选)**:默认配置已可正常使用,如需个性化调整,了解以下三个文件即可:@@ -1628,7 +1555,98 @@ GitHub 一键 Fork 即可使用,无需编程基础。👉 **详细配置教程**:[配置详解](#配置详解)-5️⃣ **🎉 部署成功!分享你的使用体验**+ <br>++5️⃣ **GitHub Actions 签到续期机制 & 远程云存储配置**:++ **v4.0.0 重要变更**:引入「活跃度检测」机制,GitHub Actions 需定期签到以维持运行。++ - **运行周期**:有效期为 **7 天**,倒计时结束后服务将自动挂起。+ - **续期方式**:在 Actions 页面手动触发 "Check In" workflow,即可重置 7 天有效期。+ - **操作路径**:`Actions` → `Check In` → `Run workflow`+ - **设计理念**:+ - 如果 7 天都忘了签到,或许这些资讯对你来说并非刚需。适时的暂停,能帮你从信息流中抽离,给大脑留出喘息的空间。+ - GitHub Actions 是宝贵的公共计算资源。引入签到机制旨在避免算力的无效空转,确保资源能分配给真正活跃且需要的用户。感谢你的理解与支持。++ ---++ **你也可以不配置远程云存储**,但此时项目处于**轻量模式**,部分高级功能不可用。++ **两种部署模式对比:**++ | 模式 | 配置要求 | 功能范围 |+ |------|---------|---------|+ | **轻量模式** | 无需配置存储 | 实时抓取 + 关键词筛选 + 多渠道推送 |+ | **完整模式** | 配置远程云存储 | 轻量模式 + 新增检测 + 趋势追踪 + 增量推送 + AI分析 |++ **轻量模式说明**:+ - ✅ 可用:实时新闻抓取、关键词筛选、热点权重排序、当前榜单推送+ - ❌ 不可用:新增新闻检测(🆕)、热度趋势追踪、增量模式、每日汇总累积、MCP AI分析++ **完整模式说明**:配置远程云存储后即可解锁全部功能,继续按下方步骤配置即可。++ <details>+ <summary>👉 点击展开:<strong>远程云存储配置(决定功能完整性)(可选)</strong></summary>+ <br>++ **⚠️ 以 Cloudflare R2 为例的配置前置条件:**++ 根据 Cloudflare 平台规则,开通 R2 需绑定支付方式。++ * **目的**:仅作身份验证(Verify Only),**不产生扣费**。+ * **支付**:支持双币信用卡或国区 PayPal。+ * **用量**:R2 的免费额度(10GB存储/月)足以覆盖本项目日常运行,无需担心付费。++ ---++ **GitHub Secret 配置:**++ **必需配置(4 项):**++ | Name(名称) | Secret(值)说明 |+ |-------------|-----------------|+ | `S3_BUCKET_NAME` | 存储桶名称(如 `trendradar-data`) |+ | `S3_ACCESS_KEY_ID` | 访问密钥 ID(Access Key ID) |+ | `S3_SECRET_ACCESS_KEY` | 访问密钥(Secret Access Key) |+ | `S3_ENDPOINT_URL` | S3 API 端点(如 R2:`https://<account-id>.r2.cloudflarestorage.com`) |++ **可选配置:**++ | Name(名称) | Secret(值)说明 |+ |-------------|-----------------|+ | `S3_REGION` | 区域(默认 `auto`,部分服务商可能需要指定) |++ > 💡 **更多存储配置选项**:参见 [存储配置详解](#11-存储配置)++ <br>++ **如何获取凭据(以 Cloudflare R2 为例):**++ 1. **进入 R2 概览**:+ - 登录 [Cloudflare Dashboard](https://dash.cloudflare.com/)。+ - 在左侧侧边栏找到并点击 `R2对象存储`。++ 2. **创建存储桶**:+ - 点击`概述`+ - 点击右上角的 `创建存储桶` (Create bucket)。+ - 输入名称(例如 `trendradar-data`),点击 `创建存储桶`。++ 3. **创建 API 令牌**:+ - 回到 **概述**页面。+ - 点击**右下角** `Account Details `找到并点击 `Manage` (Manage R2 API Tokens)。+ - 同时你会看到 `S3 API`:`https://<account-id>.r2.cloudflarestorage.com`(这就是 S3_ENDPOINT_URL)+ - 点击 `创建 Account APl 令牌` 。+ - **⚠️ 关键设置**:+ - **令牌名称**:随意填写(如 `github-action-write`)。+ - **权限**:选择 `管理员读和写` 。+ - **指定存储桶**:为了安全,建议选择 `仅适用于指定存储桶` 并选中你的桶(如 `trendradar-data`)。+ - 点击 `创建 API 令牌`,**立即复制** 显示的 `Access Key ID` 和 `Secret Access Key`(只显示一次!)。++ </details>++ <br>++6️⃣ **🎉 部署成功!分享你的使用体验**恭喜你完成了 TrendRadar 的配置!现在你可以开始追踪热点资讯了。@@ -1640,7 +1658,9 @@ GitHub 一键 Fork 即可使用,无需编程基础。👉 欢迎关注公众号「**[硅基茶水间](#问题答疑与交流)**」,你的点赞和留言都是项目持续更新的动力。-6️⃣ **想要更智能的分析?试试 AI 增强功能**(可选)+ <br>++7️⃣ **想要更智能的分析?试试 AI 增强功能**(可选)基础配置已经能满足日常使用,但如果你想要: