[{"data":1,"prerenderedAt":328},["ShallowReactive",2],{"article-static-site-cloudflare-pages":3,"article-siblings":283},{"id":4,"title":5,"body":6,"category":264,"cover":265,"date":266,"description":267,"extension":268,"meta":269,"navigation":270,"path":271,"readingMinutes":272,"seo":273,"stem":274,"tags":275,"updated":281,"__hash__":282},"articles\u002Farticles\u002Fstatic-site-cloudflare-pages.md","把动态博客彻底静态化，零成本部署到 Cloudflare Pages",{"type":7,"value":8,"toc":253},"minimark",[9,17,20,24,52,55,66,73,77,93,96,100,111,145,154,158,189,193,196,201,204,207,210,216,222,228,237,243,246],[10,11,12,13],"p",{},"动态 CMS（比如 WordPress）的每一次访问都要经过 PHP 和数据库。流量一大，或者遇到 CC 攻击，CPU 先被耗尽；程序和插件的漏洞，又给了攻击者更多下手的机会。最近一次站点被攻击到服务器 IP 被黑洞、SSH 都连不上，我索性换了思路：",[14,15,16],"strong",{},"把内容生产和对外展示彻底拆开，对外只提供静态文件。",[10,18,19],{},"下面是这套“静态化 + Cloudflare Pages”方案的完整复盘。",[21,22,23],"h2",{"id":23},"为什么选择纯静态",[25,26,27,34,40,46],"ul",{},[28,29,30,33],"li",{},[14,31,32],{},"攻击面小","：没有数据库、没有服务端脚本，对外只有 HTML、CSS、JS 和图片，常见的注入和提权手段无处发力。",[28,35,36,39],{},[14,37,38],{},"速度快","：页面直接由 CDN 边缘节点返回，首字节时间很短，也不用担心高并发把源机器压垮。",[28,41,42,45],{},[14,43,44],{},"运维轻","：不用再管 PHP 版本、数据库备份和插件升级，托管平台负责可用性。",[28,47,48,51],{},[14,49,50],{},"成本低","：Cloudflare Pages 提供免费额度，个人站点通常足够。",[21,53,54],{"id":54},"整体架构",[56,57,63],"pre",{"className":58,"code":60,"language":61,"meta":62},[59],"language-text","编辑者 ──> 私有的 WordPress（仅白名单可访问）\n                 │  静态导出\n                 ▼\n          静态文件 \u002F ZIP\n                 │  上传或 CI 推送\n                 ▼\n        Cloudflare Pages ──> 访客\n","text","",[64,65,60],"code",{"__ignoreMap":62},[10,67,68,69,72],{},"核心思想是：",[14,70,71],{},"WordPress 只负责写文章，不再面向公网","，访客看到的永远是导出后的静态结果。",[21,74,76],{"id":75},"第一步准备一个只给自己用的内容源站","第一步：准备一个“只给自己用”的内容源站",[78,79,80,83,90],"ol",{},[28,81,82],{},"准备一台 2 核 4G 左右的服务器，安装宝塔（aaPanel）等面板，用一个不对外宣传的二级域名搭起 WordPress。",[28,84,85,86,89],{},"在 Nginx 或云安全组中",[14,87,88],{},"只放行你自己的 IP","访问后台和站点。",[28,91,92],{},"之后照常写文章、排版，甚至可以借助 AI 工具辅助创作。",[10,94,95],{},"这台机器配置不用高，因为它基本没有公网访问压力。",[21,97,99],{"id":98},"第二步用插件导出全站静态文件","第二步：用插件导出全站静态文件",[10,101,102,103,106,107,110],{},"在源站安装 ",[14,104,105],{},"Simply Static"," 或 ",[14,108,109],{},"WP2Static","，以 Simply Static 为例：",[78,112,113,116,131,138],{},[28,114,115],{},"后台安装并启用插件；",[28,117,118,119,122,123,106,127,130],{},"将 ",[14,120,121],{},"Delivery Method（交付方式）"," 设为 ",[124,125,126],"em",{},"Local Directory",[124,128,129],{},"ZIP Archive","；",[28,132,133,134,137],{},"把目标地址（Destination URL）设为你",[14,135,136],{},"正式对外的域名","，这样导出的链接才是正确的；",[28,139,140,141,144],{},"点击 ",[14,142,143],{},"Generate Static Files","，插件会爬取全站链接，把文章页、图片、CSS、JS 打包成纯静态结构。",[146,147,148],"blockquote",{},[10,149,150,153],{},[14,151,152],{},"注意","：评论、搜索、会员、表单等需要服务端处理的功能在静态站上会失效。评论可以换成 Waline、Twikoo、Giscus 之类的第三方前端方案，搜索可以用 Pagefind 等纯前端索引替代。",[21,155,157],{"id":156},"第三步部署到-cloudflare-pages","第三步：部署到 Cloudflare Pages",[78,159,160,166,172,175,182],{},[28,161,162,163,130],{},"登录 Cloudflare 控制台，进入 ",[14,164,165],{},"Workers & Pages",[28,167,168,169,130],{},"选择 ",[14,170,171],{},"创建应用程序 → Pages → 上传资产（Upload assets）",[28,173,174],{},"填写项目名，把导出的目录或 ZIP 拖进去；",[28,176,177,178,181],{},"等待几十秒，会得到一个免费的 ",[64,179,180],{},"*.pages.dev"," 地址；",[28,183,184,185,188],{},"在 ",[14,186,187],{},"Custom domains"," 中绑定正式域名。",[21,190,192],{"id":191},"进阶让发布流程自动化","进阶：让发布流程自动化",[10,194,195],{},"每次发文都手动“导出 + 上传”会很烦。可以把链路串起来：",[146,197,198],{},[10,199,200],{},"文章发布 → Webhook 触发 → 自动化工具（如 n8n）执行静态导出 → 调用 Cloudflare API 或 Git 推送 → Pages 自动构建部署",[10,202,203],{},"走到这一步就能实现“写完即上线”的无人值守。",[10,205,206],{},"如果你本来就没有历史包袱，也完全可以放弃 WordPress，直接使用 Nuxt、Astro、Hugo 等静态站点生成器，用 Markdown 写文章、Git 管理内容，部署方式同样是推送到 Pages。",[21,208,209],{"id":209},"常见问题",[10,211,212,215],{},[14,213,214],{},"免费版有流量限制吗？","\n静态资源请求目前没有明显的流量上限，但单个部署有文件数量和单文件体积的限制，具体数值以 Cloudflare 官方文档为准。个人博客一般不会碰到。",[10,217,218,221],{},[14,219,220],{},"不想额外买服务器，可以吗？","\n可以。直接在本机搭 WordPress（或用 Docker），本地导出后上传即可。",[10,223,224,227],{},[14,225,226],{},"必须用 WordPress 吗？","\n不必须。任何能产出静态 HTML 的工具都行，选择取决于你的内容类型和使用习惯。",[10,229,230,233,236],{},[14,231,232],{},"这套方案最大的缺点是什么？",[14,234,235],{},"没有服务端交互能力。"," 会员、付费阅读、原生评论等都做不了，需要这些功能的站点不适合纯静态化。",[10,238,239,242],{},[14,240,241],{},"访问速度如何？","\nCloudflare 在海外表现很好；如果你的主要读者在中国大陆，需要评估线路，必要时选用对大陆更友好的 CDN 或托管方案。",[21,244,245],{"id":245},"小结",[10,247,248,249,252],{},"静态化的本质是",[14,250,251],{},"用构建时的计算换取运行时的安全与速度","。只要你的站点以阅读为主，把内容源站藏在后面、对外只托管静态文件，就能同时得到更低的成本和更强的抗压能力。",{"title":62,"searchDepth":254,"depth":254,"links":255},2,[256,257,258,259,260,261,262,263],{"id":23,"depth":254,"text":23},{"id":54,"depth":254,"text":54},{"id":75,"depth":254,"text":76},{"id":98,"depth":254,"text":99},{"id":156,"depth":254,"text":157},{"id":191,"depth":254,"text":192},{"id":209,"depth":254,"text":209},{"id":245,"depth":254,"text":245},"ops","cdn","2026-06-23","被 CC\u002FDDoS 打到服务器失联之后，我把整站改成纯静态并托管到 CDN。本文复盘“隐藏的内容源站 + 静态导出 + Pages 托管”的完整流程、限制与取舍。","md",{},true,"\u002Farticles\u002Fstatic-site-cloudflare-pages",7,{"title":5,"description":267},"articles\u002Fstatic-site-cloudflare-pages",[276,277,278,279,280],"Cloudflare","静态站点","WordPress","部署","安全",null,"rnV8251fEZv245JjyjMmVSdlrk4Jzf1uAZYwE1fOK7U",[284,287,288,292,296,300,304,308,312,316,320,324],{"path":285,"title":286,"date":266},"\u002Farticles\u002Fnew-site-cold-start-seo","新站冷启动：沙盒期怎么熬，第一批真实读者从哪里来",{"path":271,"title":5,"date":266},{"path":289,"title":290,"date":291},"\u002Farticles\u002Fsharktech-review","Sharktech 评测：自带 DDoS 清洗的老牌机房，值不值得买？","2026-06-08",{"path":293,"title":294,"date":295},"\u002Farticles\u002Fhostslick-review","HostSlick 2026 深度评测：荷兰电视塔机房里的德国主机商","2026-03-11",{"path":297,"title":298,"date":299},"\u002Farticles\u002Flinux-enable-bbr","Linux 开启 BBR 拥塞控制：原生配置与一键脚本两种做法","2026-03-09",{"path":301,"title":302,"date":303},"\u002Farticles\u002Fcms-selection-guide","内容站与导航站怎么选 CMS：WordPress 方案全流程","2026-03-05",{"path":305,"title":306,"date":307},"\u002Farticles\u002Fknownsrv-review","KnownSRV 2026 评测：荷兰与卢森堡节点的 VPS、虚拟主机与独服","2026-02-06",{"path":309,"title":310,"date":311},"\u002Farticles\u002Fbuyvm-review","BuyVM（Frantech）2026 现状：卢森堡缺货之后，它还值得买吗？","2026-01-13",{"path":313,"title":314,"date":315},"\u002Farticles\u002Fihostart-review","iHostART 评测：罗马尼亚的低价大存储 VPS，适合做什么？","2025-09-13",{"path":317,"title":318,"date":319},"\u002Farticles\u002Forangewebsite-review","OrangeWebsite 评测：冰岛老牌主机商的性能、网络与使用建议","2024-12-21",{"path":321,"title":322,"date":323},"\u002Farticles\u002Falexhost-review","AlexHost 评测：摩尔多瓦自营机房，大带宽 VPS 与独立服务器","2024-05-09",{"path":325,"title":326,"date":327},"\u002Farticles\u002Fflokinet-review","FlokiNET 评测：冰岛机房的“贵价”主机，值不值这个价？","2024-03-08",1792993223477]