From e4d609b38992dc1d3e04bdf52540ef45c500078f Mon Sep 17 00:00:00 2001
From: sansan <77180927+sansan0@users.noreply.github.com>
Date: Tue, 9 Dec 2025 13:07:58 +0800
Subject: [PATCH] =?UTF-8?q?chore:=20=E6=9B=B4=E6=96=B0=E5=85=AC=E5=91=8A?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
---
README-EN.md | 87 ++++++++++++++++++++++++++++++----------------------
README.md | 86 +++++++++++++++++++++++++++++----------------------
2 files changed, 100 insertions(+), 73 deletions(-)
diff --git a/README-EN.md b/README-EN.md
index 2e5c388..cffcf82 100644
--- a/README-EN.md
+++ b/README-EN.md
@@ -1,27 +1,7 @@
-> ## ⚠️ Important Announcement (December 2025)
->
-> Due to rapid growth in forks, GitHub has contacted me about server infrastructure strain. **This project and all forks may experience access difficulties.**
->
-> - ✅ **Recommended**: [Docker Deployment](#6-docker-deployment) (data stored locally, no restrictions)
-> - ❌ **Suspended**: Fork deployment, GitHub Actions, GitHub Pages
->
->
-> 👉 Click for details
->
-> **Issue Explanation:**
-> - Original design used GitHub Actions to periodically fetch news and save to the repository, essentially using GitHub as a "cloud database"
-> - With many forks running simultaneously, servers couldn't handle the load; GitHub engineering team is working on fixes
->
-> **Future Plans:**
-> - Exploring new approach: keep Actions for fetching and notifications, but no longer save data to repository, use external storage instead
->
-> Thanks for understanding! Feedback: [Issues](https://github.com/sansan0/TrendRadar/issues)
->
->
-
-
+> **📢 Announcement:** After communicating with GitHub officials, "One-Click Fork Deployment" will be restored after compliance adjustments are completed. Please stay tuned for **v4.0.0** update
+
@@ -63,34 +43,67 @@
-
> This project is designed to be lightweight and easy to deploy
-
-⚠️ Click to expand: Fork Guide: Docs, Resource Limits & Deployment Options
-**📄 Documentation Version:**
+
+🚨 【MUST READ】Important Announcement: The Correct Way to Deploy This Project
-If you use this project via **Fork**, you might be viewing outdated documentation. Fork copies the documentation version at that time, but the original project may have been updated.
+
-**👉 [Click to View Latest Official Documentation](https://github.com/sansan0/TrendRadar?tab=readme-ov-file)**
+> **⚠️ December 2025 Urgent Notice**
+>
+> Due to a surge in Fork numbers causing excessive load on GitHub servers, **GitHub Actions and GitHub Pages deployments are currently restricted**. Please read the following instructions carefully to ensure successful deployment.
-**How to Tell?** Check the repository address at the top of the page:
-- `github.com/your-username/TrendRadar` ← Your forked version
-- `github.com/sansan0/TrendRadar` ← Latest official version
+### 1. ✅ Only Recommended Deployment Method: Docker
+
+**This is currently the most stable solution, free from GitHub restrictions.** Data is stored locally and won't be affected by GitHub policy changes.
+
+* 👉 [Jump to Docker Deployment Tutorial](#6-docker-deployment)
---
-**🛡️ Resource Limits & Safety Tips:**
+### 2. If You Were Planning to Fork This Project...
-GitHub provides limited Actions resources per account. To avoid being flagged for abuse and risking account suspension:
+To reduce pressure on GitHub servers, **please DO NOT directly click the "Fork" button!**
-- **Platform Count**: Keep it around **10 platforms** — more platforms consume more resources
-- **Run Frequency**: Minimum interval of **30 minutes** — more frequent runs are unnecessary
-- **Fair Use**: GitHub Actions is designed for lightweight scheduled tasks, not high-frequency crawlers
+Please use the **"Use this template"** feature instead of Fork:
-💡 **Want more freedom?** Try [🐳 Docker Deployment](#6-docker-deployment) on your own server with no restrictions.
+1. **Click** the green **[Use this template]** button in the top right corner of the original repository page.
+2. **Select** "Create a new repository".
+
+**Why do this?**
+* **❌ Fork**: Copies complete history records. Many forks running simultaneously will trigger GitHub risk control.
+* **✅ Use this template**: Creates a completely new independent repository without historical baggage, more server-friendly.
+
+---
+
+### 3. About New Data Storage
+
+The new version will use **Cloudflare R2** to store news data, ensuring data persistence.
+
+**⚠️ Configuration Prerequisites:**
+
+According to Cloudflare platform rules, activating R2 requires binding a payment method.
+
+- **Purpose:** Identity verification only (Verify Only), no charges will be incurred.
+- **Payment:** Supports credit cards or PayPal (China region).
+- **Usage:** R2's free tier is sufficient to cover this project's daily operation, no payment required.
+
+---
+
+### 4. 📅 Future Plans & Documentation Reading Notes
+
+> **Future Plans:**
+> - Exploring new approach: keep Actions for fetching and pushing, but no longer save data to repository, use external storage instead.
+
+**⚠️ Reading Note:**
+Given that the above plans mean **Fork deployment mode may return in a new form in the future**, and the workload to fully revise documentation is massive, we have temporarily retained the old descriptions.
+
+**At the current stage, if "Fork" related expressions still appear in subsequent tutorials, please ignore them or understand them as "Use this template"**.
+
+👉 **[Click here to view TrendRadar's latest official documentation](https://github.com/sansan0/TrendRadar?tab=readme-ov-file)**
diff --git a/README.md b/README.md
index 63a847d..c92ba25 100644
--- a/README.md
+++ b/README.md
@@ -1,27 +1,7 @@
-> ## ⚠️ 重要公告(2025年12月)
->
-> 由于 Fork 数量激增,GitHub 官方已联系我,当前运行方式对服务器造成压力。**本项目及所有 Fork 可能出现访问困难。**
->
-> - ✅ **推荐**:[Docker 部署](#6-docker-部署)(数据存本地,不受限制)
-> - ❌ **暂停**:Fork 部署、GitHub Actions、GitHub Pages
->
->
-> 👉 点击查看详情
->
-> **问题说明:**
-> - 原设计通过 GitHub Actions 定时抓取新闻并保存到仓库,相当于把 GitHub 当"云端数据库"
-> - 大量 Fork 同时运行,服务器承受不住,GitHub 工程团队正在修复
->
-> **后续计划:**
-> - 探索新方案:保留 Actions 用于抓取和推送,但不再将数据保存到仓库,改用外部存储
->
-> 感谢理解!问题反馈:[Issues](https://github.com/sansan0/TrendRadar/issues) 或公众号
->
->
-
-
+> **📢 公告:** 经与 GitHub 官方沟通,完成合规调整后将恢复"一键 Fork 部署",请关注 **v4.0.0** 版本的更新
+
@@ -65,31 +45,65 @@
> 本项目以轻量,易部署为目标
-
-⚠️ 点击展开:Fork 须知:文档更新、资源限制与部署建议
-**📄 文档版本说明:**
+
+🚨 【必读】重要公告:本项目的正确部署姿势
-如果你是通过 **Fork** 使用本项目,你看到的可能是旧版文档。因为 Fork 时会复制当时的文档版本,但原项目可能已更新。
+
-**👉 [点击查看最新官方文档](https://github.com/sansan0/TrendRadar?tab=readme-ov-file)**
+> **⚠️ 2025年12月紧急通知**
+>
+> 由于 Fork 数量激增导致 GitHub 服务器压力过大,**GitHub Actions 及 GitHub Pages 部署目前已受限**。为确保顺利部署,请务必阅读以下说明。
-**如何判断?** 看页面顶部的仓库地址:
-- `github.com/你的用户名/TrendRadar` ← 你 fork 的版本
-- `github.com/sansan0/TrendRadar` ← 最新官方版本
+### 1. ✅ 唯一推荐部署方式:Docker
+
+**这是目前最稳定、不受 GitHub 限制的方案。** 数据存储在本地,不会因为 GitHub 策略调整而失效。
+
+* 👉 [跳转到 Docker 部署教程](#6-docker-部署)
---
-**🛡️ 资源限制与安全提示:**
+### 2. 如果你本打算 Fork 本项目...
-GitHub 为每个账号提供的 Actions 资源是有限额的。为了避免被官方判定为滥用而面临封号风险,请注意:
+为了减少对 GitHub 服务器的压力,**请千万不要直接点击 "Fork" 按钮!**
-- **监控平台数量**:建议控制在 **10 个左右**,过多平台会消耗更多资源
-- **执行频率**:建议最短间隔为 **30 分钟**,过于频繁无实际意义
-- **合理使用**:GitHub Actions 适合轻量级定时任务,而非高频爬虫
+请务必使用 **"Use this template"** 功能来替代 Fork:
-💡 **想要更自由地使用?** 推荐 [🐳 Docker 部署](#6-docker-部署),在自己的服务器上运行。
+1. **点击**原仓库页面右上角的绿色的 **[Use this template]** 按钮。
+2. **选择** "Create a new repository"。
+
+**为什么要这样做?**
+* **❌ Fork**:复制完整历史记录,大量 Fork 同时运行会触发 GitHub 风控。
+* **✅ Use this template**:创建的是一个全新的独立仓库,没有历史包袱,对服务器更友好。
+
+---
+
+### 3. 关于新版数据存储的说明
+
+新版将使用 **Cloudflare R2** 存储新闻数据,以保证持久化。
+
+**⚠️ 配置前置条件:**
+
+根据 Cloudflare 平台规则,开通 R2 需绑定支付方式。
+
+- **目的:** 仅作身份验证(Verify Only),不产生扣费。
+- **支付:** 支持信用卡或国区 PayPal。
+- **用量:** R2 的免费额度足以覆盖本项目日常运行,无需付费。
+
+---
+
+### 4. 📅 后续计划与文档阅读说明
+
+> **后续计划:**
+> - 探索新方案:保留 Actions 用于抓取和推送,但不再将数据保存到仓库,改用外部存储。
+
+**⚠️ 阅读注意:**
+鉴于上述计划意味着 **Fork 部署模式未来可能会以新形式回归**,且当前全面修改文档工作量巨大,我们暂时保留了旧版描述。
+
+**在当前阶段,若后续教程中仍出现 "Fork" 相关表述,请一律忽略或将其理解为 "Use this template"**。
+
+👉 **[点击此处查看 TrendRadar 最新官方文档](https://github.com/sansan0/TrendRadar?tab=readme-ov-file)**