adamwolfe2 cuts Mike loose from a single-vendor stack
You no longer need a Cloudflare account just to run this fork - Supabase will do.
Until now, running this fork meant committing to Cloudflare's file-storage service to hold documents. adamwolfe2 added a second option - Supabase Storage, the storage arm of a popular all-in-one backend platform - switchable with a single setting. Operators who already run on Supabase no longer have to provision a separate Cloudflare account just to store files.
The same change packages the fork for deployment on Fly.io, a hosting service, sized deliberately so document conversion doesn't run the machine out of memory - a fix informed by an earlier service that buckled under the same load. There's also a new internal entry point, locked behind its own service-level key, that lets a companion tool request document reviews machine-to-machine rather than through a logged-in user.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?