Cloudflare's EmDash got a lot of attention this week.
But if you dig into it, you need to manage a database to use it. And if you want the sandboxed plugins feature, you're basically on Cloudflare's stack.

That's fine for some projects. But a lot of Astro devs don't want that.

There's a different way worth talking about.

Use GitHub as your database. And use a Git-based CMS like Sitepins.

Your content lives in your repo with full version control, branching, and history. No database to manage. No vendor to lock you into. Your content is just files. You can still use the visual editor.

I'm part of the team building Sitepins (small bootstrap company) so take this with that context. But I genuinely think the approach is worth considering.

It works with Astro, Next.js, and Hugo out of the box. A few things worth knowing:

• It is ridiculously easy to setup. Just connect your repository, select the content folder and start editing.
• Supports MDX, iframes, has a built-in AI assistant and more..
• No database required, Git is your backend
• 1000+ users already on it

If you just want to add a CMS to your Astro site today without changing your stack, give it a shot: sitepins.com

Happy to answer questions if you've tried it or are comparing options.

I built this for www.salaryconfidential.com but figured other people may have use for it, so I've open-sourced:

fwd

- At https://github.com/qvgdlaem/fwd ), which is a link redirector you can use on your domain, subdomain and, if you have a reverse proxy, on a /namespace/* of your choice so you have branded short links.
- If you use a reverse proxy, you can designate any /namespace/ for your short links like yourmaindomain.com/go/your-short-link and you can have multiple /namespaces/ for semantic variance (go, win etc) . See below, because I open-sourced a reverse-proxy that can bind to Cloudflare workers
- You can create new shortlinks on the fly, by designating an email address for fwd (like fwd@yourdomain.com) and emailing the key:value pair. (Authentication of the email means whitelisting the email addresses that can email fwd, and setting a secret that needs to be part of the email body).

Requirement: A worker for Fwd; a D1 db for the short links and user management
And enable email on your domain for cloudflare if you want to use the Email feature)

A Cloudflare reverse-proxy

https://github.com/qvgdlaem/cf-reverse-proxy

This one can reverse proxy to other workers by bindings (score - it's so fast) or to regular url upstreams on anything (vps, railway, a bare ip, whatever

Just set up your wrangler to designate any /namespace/* to point to whatever upstream destination

Extensibility of Fwd

If you wanted to turn fwd into a clone of Linktree, it would be very easy (i debated throwing that in for free - i just have no need for this myself). All you need is extend the data model of D1 to handle a notion of an <item> with link, link text, media etc
A way to browse up the images (that you can store in D1 too) and a light bit of UI to manage the linktree screens

Anyway, it's MIT license so you can do anything you wish

I was working on a side project and needed something Redis-like, but didn’t want to deal with hosting or costs for simple use cases.

So I built a small wrapper on top of Cloudflare Workers + KV.

Important: this is NOT a replacement for real Redis. It only supports a subset of basic commands and is meant for lightweight use cases.

What it does:

• ioredis-style API (easy to plug into existing code)
• Runs on the edge
• No infra to manage
• Backed by Cloudflare KV

Install:
npm i cf-ioredis

GitHub:
https://github.com/aryanvikash/cf-ioredis

Would love feedback on:

• which commands are most needed
• real-world use cases where this fits
• limitations I should document better

S3 Explorer is a self hosted web UI that works like a normal file explorer but for your S3 buckets. Drag and drop, rename, delete, download. Works with AWS S3, Cloudflare R2, MinIO, DO Spaces, anything S3 compatible.

Store up to 100 connections and switch between them. All credentials encrypted at rest with AES 256 GCM. Deploy with Docker in 30 seconds or use Railway templates.

Open source, MIT licensed.

https://github.com/subratomandal/s3explorer