- cross-posted to:
- selfhosted@lemmy.world
- cross-posted to:
- selfhosted@lemmy.world
This is the post on reddit: https://www.reddit.com/r/selfhosted/comments/1myldh3/i_built_youtubarr_the_sonarr_for_youtube/
looks cool I have been wanting something like this for a while
IMO the trouble is that there are so many of the things now that I need a damn flowchart to understand how they work together and which ones I need.
(No, seriously: I want to set up an *arr stack but don’t understand how. Could somebody please send me a flowchart??)
It’s not a flowchart but I would recommend the following site: https://trash-guides.info/
Lots of useful info and guides
https://trash-guides.info/
Here’s a very old flow chart I made for some folks that didn’t want to use Linux. Though it mostly applies to any serup
https://github.com/Rick45/quick-arr-Stack/raw/main/img/architecture_diagram.png
For the purposes of this explanation sonarr and radarr are the same, but keep in mind that sonarr only does tv shows and radarr only does movies
You tell sonarr what you want to watch --> sonarr tells prowlarr what you want to watch --> prowlarr will search websites for magnet links to your show (you have to specify which websites) --> prowlarr will give the download manager (qbittorrent, etc) the magnet link and it will download it --> sonarr will take the downloaded file and copy it somewhere else for organizational purposes --> media server (jellyfin) will see the copied file and download associated metadata (thumbnail, episode name, episode number, etc) and allow you to watch it
The only programs you need for a purely functional arr stack are sonarr/radarr, prowlarr, qbittorrent, and jellyfin, or any other media server. Anything else is purely icing on the cake
All you actually need are sonarr (tv) radarr (movies) overseer (request management) and prowlarr (indexer management) you don’t actually need the last two.
Sorry, I tried but I couldn’t figure out how to use Flowcharr-t.