Rasputin moving out of pre-alpha [AIP]
How apps work in Rasputin — names, storage, and the catalog
An app in Rasputin is a Compose stack with a name, a target node, and a row in the control plane's database. How the names, certificates, storage and the signed app catalog actually fit together — and what is built versus designed.
Rasputin app catalog released today and, with it, Rasputin is moving from pre-alpha to alpha. Sixteen apps, each installed and opened on real Raspberry Pi and amd64 hardware.
(edit) ai-disclosure added since I forgot initially: github.com/geekdojo/…/AI_DISCLOSURE.md
Ok, and what exactly is this thing for?
Rasputin will let you take a bunch of random hardware (Pi, TuringPI, LattePanda, an old laptop, etc), homogenize them, and allow you to run apps like Home Assistant, Vault Warden, etc. on them. It takes a few minutes to get up and running and has built in DNS, Certificate Authority, Tailnet, Docker deployment, an observability stack, and supports a/b updates. AGPL license.
Basically, I was sick of always having to recreate that stack every time I rebuilt the home lab. Now it’s all baked in and flashes machines with a single bash script - managed through the control plane ui.