foolish-bandit writes the deployment manual the rest of us skipped

A documentation-only update that spells out exactly how this fork runs in production - not how it's supposed to.

infrastructure

Most forks leave anyone who wants to self-host to reverse-engineer the setup from scratch. foolish-bandit did the opposite, expanding the architecture notes nearly sixfold and adding two step-by-step guides built from the deployment path actually used, not an aspirational one.

The core insight is honest about a trade-off: the front end runs on a lightweight edge network, but the heavy lifting - converting documents and grinding through long processing jobs - lives on a conventional server, because that kind of work simply won't run in an edge environment. The guides also flag the small, silent gotchas that wreck a weekend, like a renamed configuration key that quietly breaks sign-in if you follow a generic tutorial instead of this repo's own naming.

So what If you're weighing whether to run this fork in-house, these docs are the difference between a clean afternoon and a week of guesswork.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

1 commit from foolish-bandit/gary, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
cc85fe0c docs: add detailed garyoss handoff SONOMOS 2026-05-08 ↗ GitHub

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-262.md from inside the repo you want the changes in.

⬇ Download capture-thread-262.md