I have a unused RPi4 (the 8Gig one) running DietPi. I did use it as a playground but ever since I am renting a Hetzner machine for (playground) stuff that I want web accessible, I don’t have particular use for the Pi.

I am currently running (outdated) Home Assistant on it but there isn’t much I can connect it with (yet, getting the flashable/compatible ikea smart lightning zigbee? bridge thingy is on my bucket list). Obviously I do have a pihole there.

Shoot me any other ideas I could run there. Some kind of monitoring of my rented infra would be cool (I already have uptime kuma on the dedi hetzner box). One idea I had was if there are some OSS security scanning “daemons” I could use on to monitor my other infra.

Thanks a lot!

  • @[email protected]OPEnglish
    5•8 months ago

    Why is dietpi a worse choice? it’s still basically debian (11).
    I’ve chosen DietPi because of their sane defaults that I would have to setup myself like vm swappiness, fs noatime, tmp journal, and some more I am not even aware of.

    • @TCB13English
      1•8 months ago

      Armbian has sane defaults for SBCs as well (yes log2ram so you won’t burn SD cards) and it is way more stable and polished than DietPi with less overhead. About bare Debian, you’ve the images I linked to and you can make it log to the ram with a simple line in systemd’s config.

      Storage= Controls where to store journal data. One of “volatile” (…) If “volatile”, journal log data will be stored only in memory, i.e. below the /run/log/journal hierarchy (which is created if needed).