How apps work in Rasputin — names, storage, and the catalog
rasputin.geekdojo.com
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.
  • JustEnoughDucks@slrpnk.netEnglish
    2·
    5 days ago

    I guess there is no rule about having the AI writing the AI disclosure because I guess 4 sentences has to be extended into 8 paragraphs.

    But what if the AI disclosure lies? 😂 for example, PRs are reviewed by Claude code and merged. That doesn’t sound like “every commit is reviewed by the maintainer”

    • hoodoo5x5@lemmy.worldOPEnglish
      21·
      4 days ago

      Appreciate the continued feedback.

      Some of this is me learning what each site needs/requires. I dug into it further, based on your comments (had to decipher the 4 sentences to 8 paragraphs a bit but figured it out ;) ), and read through the AI-DECLARATION schema and standards. Love that and updated and added that standard to all Rasputin repositories.

    • hoodoo5x5@lemmy.worldOPEnglish
      101·
      9 days ago

      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.