<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Cloudflare on kiwi-walk</title>
    <link>https://kiwi-walk.com/tags/cloudflare/</link>
    <description>Recent content in Cloudflare on kiwi-walk</description>
    <image>
      <title>kiwi-walk</title>
      <url>https://kiwi-walk.com/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</url>
      <link>https://kiwi-walk.com/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</link>
    </image>
    <generator>Hugo -- 0.140.1</generator>
    <language>zh-tw</language>
    <lastBuildDate>Thu, 17 Sep 2026 22:00:00 +0800</lastBuildDate>
    <atom:link href="https://kiwi-walk.com/tags/cloudflare/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Day3 [art-tracking] 技術選型：為什麼從 Vercel &#43; Supabase 搬到 Cloudflare，而不是像 coffee-review 用 GitHub Pages &#43; Supabase</title>
      <link>https://kiwi-walk.com/blogs/engineer/ironman-2026-day03-stack-and-cloudflare/</link>
      <pubDate>Thu, 17 Sep 2026 22:00:00 +0800</pubDate>
      <guid>https://kiwi-walk.com/blogs/engineer/ironman-2026-day03-stack-and-cloudflare/</guid>
      <description>Art-Tracking 第一版跑在 Vercel + Supabase 上，第二版（2026-09）整個搬到 Cloudflare Workers。這篇講為什麼不能像 coffee-review、commute 一樣用 GitHub Pages + Supabase，為什麼不留在 Vercel，以及 Hono、Drizzle、D1、R2、Vitest workers pool 這幾個選擇各自的理由與代價。</description>
    </item>
    <item>
      <title>Day2 [art-tracking] 看展追蹤器要做什麼、不做什麼：規劃時的六個取捨</title>
      <link>https://kiwi-walk.com/blogs/engineer/ironman-2026-day02-what-to-build/</link>
      <pubDate>Wed, 16 Sep 2026 22:00:00 +0800</pubDate>
      <guid>https://kiwi-walk.com/blogs/engineer/ironman-2026-day02-what-to-build/</guid>
      <description>Art-Tracking 第二版動工前，先決定它是給誰用、抓什麼、狀態怎麼分、首頁要不要逼我表態、排序聽誰的、來源壞了怎麼辦。這篇記錄六個產品面的取捨與背後的理由，以及每一個取捨落到資料模型、ingest 合約與程式碼上長什麼樣。</description>
    </item>
  </channel>
</rss>
