<?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 phinguin123</title>
    <link>http://phinguin.dev/tags/cloudflare/</link>
    <description>Recent content in Cloudflare on phinguin123</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>2026 phinguin</copyright>
    <lastBuildDate>Mon, 12 Jan 2026 16:03:00 +0900</lastBuildDate>
    <atom:link href="http://phinguin.dev/tags/cloudflare/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Planning CI/CD for Two ARM Servers</title>
      <link>http://phinguin.dev/blog/designing-ci-cd-for-two-arm-servers/</link>
      <pubDate>Mon, 12 Jan 2026 16:03:00 +0900</pubDate>
      <guid>http://phinguin.dev/blog/designing-ci-cd-for-two-arm-servers/</guid>
      <description>Planning the pipeline to replace building images by hand: where builds run, what staging is even for, which registry, and what I&amp;rsquo;d push back on now.</description>
    </item>
    <item>
      <title>What the Upstream Image Was Hiding</title>
      <link>http://phinguin.dev/blog/what-the-upstream-image-was-hiding/</link>
      <pubDate>Fri, 05 Dec 2025 12:00:00 +0900</pubDate>
      <guid>http://phinguin.dev/blog/what-the-upstream-image-was-hiding/</guid>
      <description>Splitting an all-in-one Docker image into separate services broke a bunch of assumptions I didn&amp;rsquo;t know existed. Every &amp;ldquo;how did this work before?&amp;rdquo; had the same answer.</description>
    </item>
  </channel>
</rss>
