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.
First, you should something decent, not DietPi. You’ve Armbian for a ready to go experience or official Debian.
Once you get into something Debian 12, you can run LXD/LXC as a containerization / virtualization solution and use the same Pi to run the official HA VM image and whatever else you would like.
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.
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).
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
First, you should something decent, not DietPi. You’ve Armbian for a ready to go experience or official Debian.
Once you get into something Debian 12, you can run LXD/LXC as a containerization / virtualization solution and use the same Pi to run the official HA VM image and whatever else you would like.
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.
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.