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:
- 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
I don't get why people want these for self-hosting. They're meant for GPIO and automation control. They're massively underpowered.
Just use an actual SBC and leave these for electronics.
Underpowered is probably the reason, they're small and really low powered. A pi could be a 1/10th the power consumption of an x86 computer, and thus less noise and heat.
Back in 2016 or so you could get a RaspberryPi 3 for $35. Add a $5 power supply, $5 SD card and $10 case (or 3d print your own) and you've got a nice little piece of hardware for running a tiny project at home for ~$50. More than enough for hosting some simple web services, backup software or something like Home Assistant.
Plus it was popular (which makes it even more popular). It's always been very easy to find guides written specifically for the hardware, despite it's limitations.
I think the value proposition has been dropping steadily though. They cost more, are hard to find and there are now a lot more competing SBCs on the market. RaspberryPi still has name recognition though, for now.
They're great for low strength, dedicated platforms instead of using something with more muscle like a NUC, also where a VM or container can't be used.
Out of curiosity, what are some use cases that would fit this criteria? VMs and containers are very capable and it's much easier to debug a failed VM than a failed piece of hardware.
My pending or existing projects.
A software defined radio server. Lives up top of an antenna mast running off PoE with an RTL tuner connected.
ADSB receiver, similar to above, but on a fixed frequency.
The above 2 could be virtualised in theory, but there is an advantage in having the cable to the antenna short and thus the sbcs live up antenna masts in an enclosure.
MMDVM hotspot for ham radio (this might not count as it HAS TO use the gpio pins on the pi, this can't be visualised even with a USB port passed through.
As an audio server that would bitstream 24bit/96kHz to an amp.
Primarily the external postgresql db for my k3s cluster.
I use mine to run pihole and an always-on syncthing client. Way more power-efficient than x86.
I have one behind my TV that controls LED lights, although that may count as electronics. I've used PIs many times for when I just need a cheap computer doing computery things such as playing audio from spotify out of a speaker. They're small enough to fit pretty much anywhere with the help of some velcro.
For one they make terrific 1Gbps routers with SQM. The Pi 4 has a pretty capable CPU.