I am sure I am just missing something simple… I have prowlarr -> sonarr/radarr -> qbittorrent -> jellyfin I created three directories. /jelly/video /sonarr /radarr. I configured sonarr and radar to use their respective directories. And I configured qbittorrent to use /jelly/video as the default download dir.
But what seems to be happening is that if I download a movie, it ends up in both /radarr and /jelly/video. And then if I delete it from /jelly/video it doesn’t seed for others.
What am I missing here?
The way I organized my setup was using a file structure like this:
My media player and torrent client have access to the videos directory, and Radarr and Sonarr have access to their respective directories. The *arrs add the files to the torrent client with the destination being their respective directories, and upon completion it triggers a media player library re-index. This way you can seed and stream concurrently.
So do you set the torrent client default download dir to videos? And the system is smart enough not to make a copy there because there is already one visible to the client?
Mine is a little more complicated, but it gives me piece of mind and the ability to see what each program is doing, and to manually sort files if sonarr/radarr stop working for whatever reason
My folder structure is
Each component of my stack is isolated using docker and can only acess what it needs to. Sonarr, Radarr and qbittorrent are configured to use labels to keep the downloads directory sorted.
I can post my docker-compose.yml file if you want to have a look.
So you are intentionally keeping two copies of things?
I am keeping 1 copy, with a hardlink to the other. It gets removed from qBittorrent once it has finished seeding
oh, hardlink. Linux I am guessing then? I am on windows for now. And it has been years since I tried to make a link in windows. I don’t recall it going well back then. :) So what do you mean by finished seeding? Someone else implied they only seeded to some limit. What is the story there?
Yes, however Windows offers hardlinks too, you just can’t span them across drives with either os