I only have one that's hooked up to my 3D printer for Octoprint. I'd like to set up another one as a SDR, but I leave my app hosting to more powerful machines.
I have been for about a year with one 8gb Pi 4 with a 500gb ssd. I bought it as a way to dip my toes into self hosting. Started with Home Assistant OS, but now I have a bunch of containers set up, such as Home Assistant, Plex, Sonarr, Radarr, Prowlarr, qbittorrent, and a few others. I will eventually get something a little beefier to host my media, but will absolutely keep the Pi running.
Use an old Pi 3B for running zigbee2mqtt on docker.
I used to run just the Linux version of it but decided to install docker on the Pi so it's as easy as doing docker-compose pull
to update it.
This is so I can control my various lights and switches using Home Assistant.
I currently have Pi-hole and Unbound running on my pi4
I have a pi zero running as a doorbell camera, alongside a couple more CCTV cameras, and a pi4 running in kiosk mode connected to my motioneye server displaying said camera streams on a crappy old TV in my home office.
I run AdGuard Home (mostly for malware domain blocking and DNS caching) on my home server, and the Pi acts as a secondary DNS server. I use AdGuardHome-Sync to keep the config in sync across the two.
I've got several for random little tasks that crop up, but main use is for the conbee II I have running the zigbee network for all the smart lights. I've got a UPS hat using some old 26650 cells for battery backup, mostly so that if power cuts off I don't run into any issues with the setup and the rare cases where I have to take the power off the server rack for whatever reason. RPi has actually been rock solid for couple years now so no issues with that side, wife approval factor has likewise been high
Also got a Turing Pi but haven't had a change to play with it too much yet. For most everything else I'm running a docker and VMs in TrueNAS, but would probably change that setup at some point..
I have a couple of Pis, but currently only using the Pi 4 which is my Kodi box (LibreELEC). I planned to use my older Pi 3B as a web server, but I also have Proxmox on a NUC running as my main home server, so I don't know if there's any advantage to using the Pi at this point.
use it for home assistant. I'm astonished because my test install from years ago on a pi that's around 7 years old is going with no intervention aside from updates. it's crazy robust.
for a while my laptop was slow and I needed a test local environment rebuilding with webpack so I set up a newer pi that ran the Dev servers so my laptop didn't choke. I've got a better laptop now.
I've got one as a Pi Hole, one as a Kodi box, and a few others I keep around as basically electronic multitools.
Pi 4 running Home Assistant.
A second one sitting in a box meant to be the first of a cluster, until they disapeared
One for home assistant, one for very basic network services (dns, auth, dhcp) that I want up all the time even if I have to shut down the router+firewall. If I have to upgrade the firewall box I don't want to be unable to print, or use smart home stuff.
Home Assistant setup, along with media hosting for a hard drive full of all my music and movies.
One for pihole
I used one in the past for Unify Controller but it broke
Another one is a USB wifi hub to control my telescope equipment remotely.
I use a pi 3 to host backups from my main server via restic. I also have a pi 4 that I use as a VPN server
Yes, a Pi 4 with 2GB RAM. It is running Navidrome (music server) with my music collection on a 2TB SSD connected to it. Works great.
The energy consumption at around 3-4 W, pretty neat!
I used a pi 3 to host a Foundry server (TTRPG software).
I use Docker to simplify things, since I run two instances of it. Simple port forwarding setup within the docker container. the main reason I used a pi instead of my computer is so my players could access their dnd stuff all the time.
I stopped because I switched ISPs and they won't let me port-forward. My vpn supports it but the latency isn't ideal. I host the same thing through a cheap server now.
Incase you wanna go back to port forwarding, you could try ipv6! Just gotta make sure all your party members computers have ipv6 enabled
One runs Home Assistant (Pi4), and an older one runs RetroPi (Pi3) for my arcade cabinet.
I have another Pi3 that I used to use as a Steam Streaming device to put my PC games on the projector.
I'm only using Pi 4 hardware:
- OpenWrt gigabit routers with SQM, multiple locations
- Home Assistant Yellow
- NAS with RAID1 (mirror), deprecated
I have a single Raspberry Pi 3b as a local file/media server running Jellyfin. I'm also running BOINC and seeding torrents of various Linux distributions. External HDD for storage, plus a thumb drive for the local media and another for the torrents so it only has to spin up when someone's actually using it.
It's not super-fast by any means, but it's fast enough to listen to music over my LAN, which is the main thing I need it to do quickly. Though eventually I plan on setting up a better NAS on something with faster I/O.
I have a 2 running teamspeak for gaming with my wife (separate rooms and don't want to yell) and pihole. And a 3 hooked to a 3d printer running octoprint.
I have 3 of the 3rd generation ones to mess around on.
I have four Pis. They're running Pihole DNS & DHCP, a reverse proxy, and torrent clients. I don't have them setup as a cluster, been meaning to look into it but I don't want to add complexity so I'm putting it off.
K3's cluster, Gitlab, Ghost, Nextcloud, Elastic stack, and some other stuff.
Using a Pi3b to run AdGuard Home and a TailScale subnet router.
I've got another Pi3b running Octoprint/Klipper for a 3d printer, but I'm currently migrating that to Mainsail running on an old SFF PC so I can run multiple printers with Klipper off the same PC.
The rest of my stack is on an actual server running UnRaid with like 50tb raw storage.
I will say that TailScale has been annoying asf with their subnet router setup not actually forcing the correct DNS for AdGuard Home so I can have ad-blocking while away from home. I had to move back to a pure Wireguard setup directly on my router for DNS to work properly.
I use it for WOL on my PC
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
Fewer Letters | More Letters |
---|---|
DNS | Domain Name Service/System |
HA | Home Assistant automation software |
~ | High Availability |
HTTP | Hypertext Transfer Protocol, the Web |
IP | Internet Protocol |
MQTT | Message Queue Telemetry Transport point-to-point networking |
NAS | Network-Attached Storage |
NUC | Next Unit of Computing brand of Intel small computers |
PiHole | Network-wide ad-blocker (DNS sinkhole) |
Plex | Brand of media server package |
RPi | Raspberry Pi brand of SBC |
SATA | Serial AT Attachment interface for mass storage |
SBC | Single-Board Computer |
SSD | Solid State Drive mass storage |
SSH | Secure Shell for remote terminal access |
VNC | Virtual Network Computing for remote desktop access |
VPN | Virtual Private Network |
VPS | Virtual Private Server (opposed to shared hosting) |
Zigbee | Wireless mesh network for low-power devices |
nginx | Popular HTTP server |
[Thread #170 for this sub, first seen 27th Sep 2023, 16:05] [FAQ] [Full list] [Contact] [Source code]
I have Home Assistant on one and Kodi (Libreelec) on another
I use a Pi4 to run one of my HAproxy nodes. It does die once in a while from not enough power because my power brick is pretty old at this point. Other than that its great. I used to have a cluster of Pi3's bit I'm transitioning cluster managment systems so they aren't doing anything right now. I recently got a Lichee pi and that will most likely replace them once I get it all working.
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!