Back to articles
Why I Open-Sourced My Hardened *arr Stack (and What Most Compose Files Get Wrong)
How-ToTools

Why I Open-Sourced My Hardened *arr Stack (and What Most Compose Files Get Wrong)

via Dev.toPrzemysław Mroczek

My name is Przemek and I have a problem with commercial streaming services. It started when I saw a proper 4K Blu-ray remux on my OLED TV. The bandwidth was 60 Mbps, zero compression artifacts, no banding in the blacks. I wasn’t aware what I was missing. Most streaming services push maybe 15 Mbps for their "4K." It's not even close. So like any tech obsessed person, I went down the self-hosted media rabbit hole. Jellyfin, Sonarr, Radarr, the whole *arr ecosystem, Unraid OS, and buying a Terramaster and then modifying it. The pipeline itself is well-documented. What isn't well-documented is how to run it without feeling that something is off about your settings. I looked at dozens of Docker Compose files across GitHub, Reddit, YouTube tutorials. They all had the same problems, and nobody seemed to care. The r/selfhosted is mostly hobbyist, which hack things together by duct tape and don’t see the difference between infra as code and clicking things through portainer. The state of most *

Continue reading on Dev.to

Opens in a new tab

Read Full Article
3 views

Related Articles