<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>S3 on Tai&#39;s Life</title>
    <link>https://taislife.work/tags/s3/</link>
    <description>Recent content in S3 on Tai&#39;s Life</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 31 May 2024 10:22:49 +0800</lastBuildDate>
    <atom:link href="https://taislife.work/tags/s3/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>[Tutorial] Build a Free Image Hosting System for Hugo with Cloudflare R2 and Workers</title>
      <link>https://taislife.work/blogs/cloudflare-r2-4-hugo-shortcode/</link>
      <pubDate>Fri, 31 May 2024 10:22:49 +0800</pubDate>
      <guid>https://taislife.work/blogs/cloudflare-r2-4-hugo-shortcode/</guid>
      <description>&lt;h2 id=&#34;preface-why-use-cloudflare-r2-for-hugo-image-hosting&#34;&gt;Preface: Why Use Cloudflare R2 for Hugo Image Hosting?&lt;/h2&gt;&#xA;&lt;p&gt;When running a static site built with Hugo, image management is always a hot topic. The traditional approach is to dump image files directly into the project&amp;rsquo;s &lt;code&gt;static/&lt;/code&gt; directory and commit them to Git version control along with the code. However, as the number of images grows, this method can cause your Git repository to become ridiculously bloated. This not only slows down &lt;code&gt;git clone&lt;/code&gt; and &lt;code&gt;pull&lt;/code&gt; operations but also makes backups and management a real headache.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
