🌟 Self-Hosting Journey Update! 🌟

After weeks of work, I'm excited to share my self-hosted setup! 🎉 I'm running everything on a Raspberry Pi 500 with Stormux (Arch Linux ARM-based), 8 GB RAM, and a 512 GB SD card (planning to upgrade to SSD or NAS as soon as I can afford it). Here's what I’ve built so far:

🔧 Services in Action:
Development: Forgejo, Code-Server, Woodpecker CI
Productivity: Joplin Server, Monica CRM, Homepage dashboard
Monitoring: Prometheus + Alertmanager, Grafana, Netdata, Uptime Kuma
Networking: AdGuardHome + Unbound, Tailscale VPN
Tools: MiniFlux, Linkding, TheLounge
Management: Portainer, Cockpit, Watchtower

🔒 Security & Access:
Caddy + Cloudflare Zero Trust/Access for reverse proxy & SSO
FirewallD + Fail2ban for extra protection

📧 Emails Powered by Zoho ZeptoMail:
All email-capable services (e.g., Forgejo, Joplin) are configured for reliable notifications.

💾 Backups: Using IDrive's 5 TB plan for peace of mind.

This journey has been challenging yet rewarding! 🚀 I'd love to hear your thoughts—especially tips on scaling storage or optimizing performance. Let's chat! 💬

SelfHosting #RaspberryPi #Linux #ArchLinuxARM #Stormux #Tech #OpenSource #DIYTech #HomeLab #CloudComputing #AdGuardHome #Grafana #Prometheus #CodeServer #Portainer

@selfhost @selfhosted @selfhosting

You're viewing a single thread.

8 comments

I really love home labs but this sounds incredibly over engineered for its purpose... I would expect a set up like this for an enterprise environment...
- @Xanza Not sure what you mean. I wanted to use my services with my domain. I tried a reverse proxy by itself and it wouldn't work because my ISP blocks ports, so I set up Cloudflare instead. Then I found out my services would work better with Caddy, so I set that up. I also originally wasn't using Unbound, but then I realized my services were having trouble communicating, and I thought it would help to have more control over DNS rules, which it has.
  
  Then I found out my services would work better with Caddy
  Exceptional idea. Cloudflare is nice, but Caddy will always win IMO. Additionally, considering you were able to get Caddy working, that simply drives home that unfortunately your reverse_proxy didn't work because it was somehow misconfigured. Caddy is also a reverse_proxy.
  My comment is pretty much what I said. You have an extremely complex environment that you're not fully making use of. For example, you're having issues with a reverse_proxy, but you had Tailscale presumably the whole time. Why not just use your VPN to reverse_proxy your requests if you were having issues?
  Also using Caddy + Cloudflare is fine if you want to use cloudflare for DNS, however, Caddy handles all certificates itself. So you have Caddy, which can handle all the SSL certs itself, but you put Cloudflare on top of it to manage SSL certs. It's just convoluted.
  It's a good environment, but a little overkill.

8 comments