|
|
|
|
|
by cantagi
1253 days ago
|
|
I have 3 rpi4s running my entire home network. One is a vpn router and a wifi AP, it also has Uptime Kuma. I need this to be reliable and rarely touch it except to improve its reliability.
- Openvpn
- HostAPD
- Uptime Kuma (in docker)
- A microservice invoked from Uptime Kuma that monitors connectivity to my ISPs router (in docker)
- nginx, not in docker, reverse proxies to Uptime Kuma The second acts as a NAS and has a RAID array, consisting of disks plugged into a powered USB hub. It runs OpenMediaVault and as many network sharing services as I can set up. I also want maximum reliability/availability from this pi, so rarely touch it. All the storage for all my services is hosted here, or backed up to here in the case of databases that need to be faster. The third rpi runs all the rest of my services. All the web apps are dockerized. Those that need a DB also have their DB hosted. Those that need file storage are using kerberized NFS from my NAS. This rpi is also another wifi AP. This rpi keeps running out of RAM and crashing and I plan to scale it when rpis become cheaper or I can repair some old laptops.:
- Postgres
- HostAPD
- nginx
- Nextcloud
- Keycloak
- Heimdall
- Jellyfin
- N8N
- Firefly-iii
- Grist
- A persistent reverse SSH tunnel to a small VM in the cloud to make some services public
- A microservice needed for one of my hobbies
- A monitoring service for my backups All of these pis are provisioned via Ansible. |
|
I used to use a single RP to run as a media server, and it was great, but stopped using it after suffering from SD card corruption.