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.
So this implies there is something else I am missing. I assumed people would just keep the whole library open for seeding. Why would you want to delete the file in the download folder?
You would delete the download to completey stop seeding.
Take a look at the guides others have posted.
My structure is this:
torrent
-movies
-TV
media
-movies
-TV
qbit downloads to the torrent folder where it seeds out from. Radarr/Sonarr make a Hardlink copy from the torrent folder to the media folder. Your media software watches the media folder.
I mean that’s up to you, my personal settings are 2:1, it’ll delete and stop seeding once it’s uploaded as much as 2 downloads worth.
But it’s important to remember that Radarr/Sonarr are Usenet first, torrents didn’t have official support till fairly recently and it’s still a little wonky
Officially, to seed you basically have to have a duplicate file until your set threshold is reached.
If you want to seed forever (or at least a really long time (ty btw for your contributions)) I’d say you’re probably going to want some custom scripts. Have Radarr move the file and rename as normal and then your script to symlink it back to the torrent directory under the original filename so it can continue to seed without taking up double space for every movie
torrents didn’t have official support till fairly recently and it’s still a little wonky
I don’t think this is true at all. They’ve both had solid torrent support for years, across multiple major version numbers. It’s neither wonky nor recent.
I’d say you’re probably going to want some custom scripts. Have Radarr move the file and rename as normal and then your script to symlink it back to the torrent directory under the original filename so it can continue to seed without taking up double space for every movie
Further driving home that this dude is full of shit, hardlinking the files is enabled by default in both Sonarr and Radarr and certainly doesn’t require any custom scripting.
OP, quit listening to random people online and spend some time reading the documentation yourself.
Many people do not want to seed downloaded content forever for storage reasons. In these cases, you would download the file with your download client and leave it in that download directory to allow seeding. It’ll be hardlinked to the Radarr/Sonarr folder for indexing, which does not use up extra storage space. Once a certain seeding/time goal is reached on the torrent, the torrent file will be deleted to make room for new torrents. This does (to my knowledge) not delete the file from the disk, meaning it is still accessible for your media center.
Especially for people who run their software on hosted solutions with limited storage space, this is important to do. If you have all your software running on a local server with (virtually) infinite storage, this is not as much of a worry to you. It is probably still in your best interest to use hardlinks instead of copies, to save on storage space.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !piracy@lemmy.dbzer0.com
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
So this implies there is something else I am missing. I assumed people would just keep the whole library open for seeding. Why would you want to delete the file in the download folder?
You would delete the download to completey stop seeding. Take a look at the guides others have posted.
My structure is this:
torrent -movies -TV
media -movies -TV
qbit downloads to the torrent folder where it seeds out from. Radarr/Sonarr make a Hardlink copy from the torrent folder to the media folder. Your media software watches the media folder.
but why would you want to stop seeding?
I mean that’s up to you, my personal settings are 2:1, it’ll delete and stop seeding once it’s uploaded as much as 2 downloads worth.
But it’s important to remember that Radarr/Sonarr are Usenet first, torrents didn’t have official support till fairly recently and it’s still a little wonky
Officially, to seed you basically have to have a duplicate file until your set threshold is reached.
If you want to seed forever (or at least a really long time (ty btw for your contributions)) I’d say you’re probably going to want some custom scripts. Have Radarr move the file and rename as normal and then your script to symlink it back to the torrent directory under the original filename so it can continue to seed without taking up double space for every movie
I don’t think this is true at all. They’ve both had solid torrent support for years, across multiple major version numbers. It’s neither wonky nor recent.
Further driving home that this dude is full of shit, hardlinking the files is enabled by default in both Sonarr and Radarr and certainly doesn’t require any custom scripting.
OP, quit listening to random people online and spend some time reading the documentation yourself.
Many people do not want to seed downloaded content forever for storage reasons. In these cases, you would download the file with your download client and leave it in that download directory to allow seeding. It’ll be hardlinked to the Radarr/Sonarr folder for indexing, which does not use up extra storage space. Once a certain seeding/time goal is reached on the torrent, the torrent file will be deleted to make room for new torrents. This does (to my knowledge) not delete the file from the disk, meaning it is still accessible for your media center.
Especially for people who run their software on hosted solutions with limited storage space, this is important to do. If you have all your software running on a local server with (virtually) infinite storage, this is not as much of a worry to you. It is probably still in your best interest to use hardlinks instead of copies, to save on storage space.