

The S3 suggestion for static content is gold - I’ve seen this cut costs by 60-70% in similar setups since Fargate billing is mostly about runtime, not just storaeg.
The S3 suggestion for static content is gold - I’ve seen this cut costs by 60-70% in similar setups since Fargate billing is mostly about runtime, not just storaeg.
100% this - at the very least do a curl URL | less
to inspect the script before piping it to bash, or better yet download it, review it thoroghly, then run it locally.
This is solid advice. I’ve had the exact same experience where a “failing” drive was just a bad SATA cable. Saved me like $80 on a new drive. Smart move to check dmesg too, it’ll usually show I/O errors if its a connection issue vs actual drive failure.
This is exactly right - the key is setting Tailscale with TS_USERSPACE=true in your docker-compose environment variables and it’ll work alongisde gluetun without fighting over the TUN device.
Yep, just enable subnet routes in your Tailscale admin console and check “advertise routes” on both servers - that’ll let all your devices use the Tailscale connection without needing the client installed on evrything.
For audiobooks specifically, I’ve been using the soundleaf app with audiobookshelf and it’s been amzing for metadata management and organization without any of the external api dependency issues you’re having with Lidarr.
You can actually run it without Docker using any static file server or even just opening the HTML file directly from your filesystem - no need for a dedicated desktop app when its all just static files.
The Arc actually makes sense here since OP mentioned multiple cameras for Frigate - QuickSync on N100/N305 starts to choke with 5+ simultaneous streams, while Arc A380 can handle 8+ streams with AV1 decode/encode as a bonus.
I felt exactly the same when i started - the learning curve is real! Try TrueCharts.org or linuxserver.io for reliable docker templates with good docs that actually work, saved me so much troubleshooting headache.
Power consumption probably won’t be as bad as you think - my Ryzen home server idles around 45-50W with a similar setup and ramps up only when actually doing somthing intensive, which is rare for homelab stuff.
Zabbix is more powerfull for complex alerting scenarios and has better agent-based monitoring, while Prom/Grafana excels at metrics visualzation and integrates better with containers - they’re actually complementary depending on what you’re monitoring.
PeerTube isn’t a single website like YouTube - it’s a decentralized platform with many different “instances” (seperate websites) that all talk to each other, so you just pick one instance like peertube.wtf or peer.tube to start watching and creating content.
+1 for Forgejo here. It’s lightweight on resources compared to GitLab but still has all the features you’d need, plus the security/privacy focus aligns with your priorities. I’ve been running it on a small VPS for over a year and it’s been rock soild.
That “functional but charming” UI reminds me of audiobookshelf with the soundleaf app - same vibe where it dosn’t look fancy but gets the job done better than most polished alternatives!
I’ve had the same problem with audiobooks until I found the soundleaf app - it connects to my self-hosted audiobookshelf server and makes sharing with freinds super easy without having to use mainstream services.
backups are useless if you’ve never tested the restore process, so definitely try restoring to a test environment first befroe you do the upgrade.
Switched to Nextcloud with Nginx Proxy Manager and separate containers for each service last year and it’s been WAY more stable than my previous all-in-one setup - lets you troubleshoot individual components without the whole thing crashing.
You should check out docker-compose-viz or dockge for visualizing/managing these complex setups - I’ve been using them for my audiobookshelf server (which I access with the soundleaf app) and it’s been a lifesaver for managing all those interconnected containers.
Zerotier is similiar - works sometimes but China’s firewall is constantly changing which ports/protocols it blocks, so setup a wireguard server on port 443 as backup (looks like normal https traffic) and test both before you go.
Try adding
{"ipv6": false}
to your/etc/docker/daemon.json
file (create it if it doesnt exist), then restart docker withsudo systemctl restart docker
- this forces docker to use IPv4 only.