From 5ef48de5c9c1f4068062a27ec90c70e0cc81199f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=E4=BA=8C=E5=8F=89=E6=A0=91=E6=A0=91?= <acofork@qq.com>
Date: Sun, 4 Jan 2026 02:53:52 +0800
Subject: [PATCH] =?UTF-8?q?posts:=20=E6=9B=B4=E6=96=B0uptimeflare=E6=96=87?=
 =?UTF-8?q?=E7=AB=A0=E6=B7=BB=E5=8A=A0=E8=BF=81=E7=A7=BB=E6=8C=87=E5=8D=97?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

添加从KV迁移到D1的详细步骤说明，帮助旧版用户升级
---
 src/content/posts/uptimeflare.md | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/src/content/posts/uptimeflare.md b/src/content/posts/uptimeflare.md
index 86c3c9c0d..84207ade3 100644
--- a/src/content/posts/uptimeflare.md
+++ b/src/content/posts/uptimeflare.md
@@ -6,6 +6,19 @@ image: ../assets/images/uptimeflare.png
 draft: false
 lang: ""
 ---
+# 从KV迁移
+由于原项目于26/1/3将数据存储从KV迁移到了D1，并且配备了完备的i18n，如果你仍在运营旧版的UptimeFlare，建议升级，下面是迁移教程
+
+首先，将你之前配置的Cloudflare API令牌添加一个新的权限 **编辑D1**
+
+然后备份根目录的 `uptime.config.ts` ，直接 把原仓库删了，Fork我的仓库
+
+::github{repo="afoim/UptimeFlare"}
+
+接下来编辑新的 `uptime.config.ts`
+
+参阅 [UptimeFlare/uptime.config.ts at main · afoim/UptimeFlare](https://github.com/afoim/UptimeFlare/blob/main/uptime.config.ts) 主要就是将自定义callback迁移到官方的WebHook方法
+
 # 前言
 本来这个教程应该是永远都不会出的，因为在此之前，我曾经给大家介绍了一个无需自托管的监控服务：[UptimeRobot](/posts/uptimerobot/)