<?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 Keldo.uk</title>
    <link>https://keldo.uk/tags/cloudflare/</link>
    <description>Recent content in Cloudflare on Keldo.uk</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 08 Oct 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://keldo.uk/tags/cloudflare/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Cloudflare pages</title>
      <link>https://keldo.uk/cloud/cloudflare-pages/</link>
      <pubDate>Wed, 08 Oct 2025 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/cloud/cloudflare-pages/</guid>
      <description>&lt;p&gt;I recently noticed that my free tier cloudflare included cloudflare pages. I spent a while thing what small website i could fit on its limited compute. Around the same time I had been getting annoyed with my Up-time Kuma filling my inbox every time my services took to long to respond so i decided to try and setup a up-time tracker.
After a quick google search I found &lt;a href=&#34;https://github.com/lyc8503/UptimeFlare&#34;&gt;UptimeFlare&lt;/a&gt; it seemed to included the functionality i needed so i copied the template. I then went into the cloudflare workers dashboard and linked the repo to a new project. However, the build failed again and again after several attempts i went back to the repo to look for any config options related to the errors. At that point I finally noticed the deploy workflow included with the repo. This worked first time of course. The config was easy however i currently have no need of the maintenance options.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
