I recently moved my personal blog from a PHP setup to Astro on Netlify because I wanted to add ActivityPub support with Fedify.
Somehow, it took me until then to realize that I had never actually tried running Fedify on Netlify.
Netlify Database is PostgreSQL, so the persistence side should already fit @fedify/postgres. The less obvious part is background delivery: Netlify Functions cannot keep a queue consumer alive, while Async Workloads uses a push-based model similar to WorkersMessageQueue in @fedify/cfworkers.
So I’m going to try making @fedify/netlify, with my own blog as its first real test case. I wrote down the initial design in issue #930.
github.com
`@fedify/netlify` for Netlify Async Workloads · Issue #930 · fedify-dev/fedify
Background Fedify can serve federation requests from Netlify Functions through the standard Request and Response APIs. Persistent state also does not need a Netlify-specific adapter: Netlify Databa...