Selfhosted
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).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
Pi 4's were hard to get there for a while. Pi 5's are expensive. Lot of other SBCs are also expensive, as in not all that much cheaper than a 2-3 generations old low-end x86. That makes them less attractive for special purpose computing, especially among people who have a lot of old hardware lying around.
Any desktop from the last decade can easily host multiple single-household computer services, and it's easier to maintain just one box than a half dozen SBCs, with a half dozen power supplies, a half dozen network connections, etc. Selfhosters often have a 'real' computer running 24/7 for video transcoding or something, so hosting a bunch of minimal-use services on it doesn't even increase the electric bill.
For me, the most interesting aspect of those SBCs was GPIO and access to raw sensor data. In the last few years, 'smart home' technology seems to have really exploded, to where many of the sensors I was interested in 10 years ago are now available with zigbee, bluetooth or even wifi connectivity, so you don't need that GPIO anymore. There are still some specific control applications where, for me, Pi's make sense, but I'm more likely to migrate towards Pi-0 than Pi-5.
SBCs were also an attractive solution for media/home theater displays, as clients for plex/jellyfin/mythtv servers, but modern smart-TVs seem mostly to have built-in clients for most of those. Personally, I'm still happy with kodi running on a pi-4 and a 15 year old dumb TV.
This is how I feel.
I would much rather have a single machine running vms which I can easily snapshot and back up rather than a dozen small machines I have to deal with power supplies and networking.
SBCs have specific use cases, usually where they need to interact with hardware. That's what made the rpi so great with it's GPIO and hats. But that's a rather small use case.
I have pi4 with OpenMediaServer for SMB shares and videos to TV, it has docker and portainer add ins; so that single Pi has CUPS, Trillium Notes, PaperlessNG, homeassistant, kanboard, pdftk converter, syncthing. It could have more, I just ran out of applications I might need. no issues with performance.
My pi4 8gb is awful as a jellyfin client am I doing something wrong? Pi OS, and just using Firefox to watch. CPU/GPU were maxed out, ram usage like 1gb
Which codecs do you have in your library? Also which resolution/bitrate?
Also, have a look at Kodi as a client.
My guess is Firefox. I'm using Kodi - OSMC/libreelec - and it coasts along at 1080p, with plenty of spare CPU to run pihole and some environmental monitors. Haven't tried anything 4k, but supposedly Pi4 offloads that to hardware decoding and handles it just fine. (as long as the codec is supported).