The saga

Well… it worked for me.

Somewhere out there a bug is reproducing flawlessly on your machine and refusing to exist on ours. This is that story. It has no happy ending — only a deploy.

RBDhub runs on the homelab equivalent of duct tape and stubbornness: a stack of secondhand servers, one heroic Mac mini, and a GPU that would rather be gaming. Things break. Then they un-break. Then they break in a new and exciting way we hadn't budgeted for. We call that experimental and ship it anyway.

The debugging loop, documented

  1. Reproduce the bug. Fail to reproduce the bug.
  2. Add a log line. The bug vanishes. Remove the log line. It returns.
  3. Blame the network. Apologize to the network.
  4. Restart it. It works. Nobody knows why. Do not touch it.
  5. Push to prod. "It worked for me."
Occasional hiccups are a feature.

Our position, stated plainly

Buttons mostly work. When they don't, we call it experimental and poke it just to be sure. We triage with optimistic efficiency. Beta first, stable later — rapid updates, rapid regrets, rapid fixes. If something here is broken right now, congratulations: you found the edge of the map. Tell us in Discord and we'll pretend we already knew.

That's the whole saga. It worked for me. It will probably work for you. Shelf esteem: high.

Get the launcher Back to the chaos

— RBDhub. Research it. Build it. Deploy it. (Mostly functional.)