Someone help me understand the sonarr to jellyfin workflow
So I've got jellyfin all set up, but I'm having some issues with files downloading from qbittorrent and Knowing exactly how and when they get moved over, either the sonar or jellyfin repository, whichever is the final destination. This is important because my torrenting drive is separate from my media drive. I have noticed some shows and files staying on my torrenting drive while others go over to the media drive. And I'm and to figure out where the issue might be that's causing this, I think I need a refresher on exactly how and when these files are supposed to be moved over. Since I can't find any sort of documentation inside the apps.
Can anybody explain this to me like super simply? I just took an edible and it's starting to kick in, but I still want to figure this out. Thanks y'all!
I’ve literally just set this all up and it’s working now after some tinkering, so here’s what I found out. Assuming you have correctly configured the sonarr/qbitorrent api keys and credentials:
When you make a TV show request in Sonarr, it will automatically add the torrent to your download client (e.g qbitorrent)
qbitorrent will then download the file to wherever you specify (e.g. /torrents/completed)
periodically, Sonarr will scan that /torrents/completed folder, and if it finds the tagged TV show, it will either copy or hard link that video file to your specified media folder (e.g. /media/tv-shows)
JellyFin will do the same, periodically scanning your media folders to see if there are any updates
EDIT: also if you are using docker containers, make sure that Sonars native /downloads folder is pointed at the same external folder your qBitTorrent is downloading files in
I think Sonarr uses qBittorrent's (or other supported torrent client) API for checking the progress, instead of periodic scans. Everything else is solid.