<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: yuit axiba</title>
    <description>The latest articles on DEV Community by yuit axiba (@yuit_axiba_b211c7ed6c643d).</description>
    <link>https://dev.to/yuit_axiba_b211c7ed6c643d</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4005005%2F5c057b5a-dba3-4b50-a1b8-454e5aa71324.png</url>
      <title>DEV Community: yuit axiba</title>
      <link>https://dev.to/yuit_axiba_b211c7ed6c643d</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/yuit_axiba_b211c7ed6c643d"/>
    <language>en</language>
    <item>
      <title>I built a personal image hosting and file manager on Cloudflare Workers</title>
      <dc:creator>yuit axiba</dc:creator>
      <pubDate>Sat, 27 Jun 2026 07:48:19 +0000</pubDate>
      <link>https://dev.to/yuit_axiba_b211c7ed6c643d/i-built-a-personal-image-hosting-and-file-manager-on-cloudflare-workers-4jko</link>
      <guid>https://dev.to/yuit_axiba_b211c7ed6c643d/i-built-a-personal-image-hosting-and-file-manager-on-cloudflare-workers-4jko</guid>
      <description>&lt;p&gt;I wanted a small image hosting service that I could deploy without maintaining a server.&lt;/p&gt;

&lt;p&gt;Most image hosting tools I tried were either too tied to one storage provider, too simple for file management, or required me to maintain a traditional backend. So I built ImgBed around Cloudflare Workers.&lt;/p&gt;

&lt;p&gt;It is designed for personal image hosting and lightweight file hosting. The main idea is simple: use Cloudflare as the deployment and runtime layer, then manage uploads, files, API tokens, and storage channels from a web UI.&lt;/p&gt;

&lt;p&gt;What it currently supports:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Deploying to Cloudflare Workers or Pages&lt;/li&gt;
&lt;li&gt;File upload and file management&lt;/li&gt;
&lt;li&gt;API Token based upload, list, delete, and file management&lt;/li&gt;
&lt;li&gt;Multiple storage channel configuration&lt;/li&gt;
&lt;li&gt;Basic security settings such as upload restrictions and token permissions&lt;/li&gt;
&lt;li&gt;A deployment flow for users who do not want to configure everything manually&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The stack is mostly:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Cloudflare Workers / Pages&lt;/li&gt;
&lt;li&gt;Cloudflare D1&lt;/li&gt;
&lt;li&gt;Cloudflare KV&lt;/li&gt;
&lt;li&gt;Vue frontend&lt;/li&gt;
&lt;li&gt;API Token based management endpoints&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;One thing I spent a lot of time on was deployment UX. Cloudflare is powerful, but small things like missing KV/D1 resources, OAuth permissions, or workers.dev URL settings can be confusing for new users. So I added step-by-step deployment progress and clearer error messages.&lt;/p&gt;

&lt;p&gt;For example, if the Workers production URL is not enabled, the deployment page now tells the user exactly what to enable instead of just showing a generic failure.&lt;/p&gt;

&lt;p&gt;Docs:&lt;br&gt;
&lt;a href="https://github.com/axibayuit-a11y/imgbed-docs" rel="noopener noreferrer"&gt;https://github.com/axibayuit-a11y/imgbed-docs&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I am still improving the documentation and the deployment flow. Feedback from people who use Cloudflare Workers, D1, KV, or self-hosted image/file &lt;br&gt;
tools would be very helpful.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
