search

pymedusa / Medusa

Automatic Video Library Manager for TV Shows. It watches for new episodes of your favorite shows, and when they are posted it does its magic.
https://pymedusa.com
GNU General Public License v3.0
1.81k stars 276 forks source link

Post-processing option: move using "move storage" feature of torrent clients #7789

Open Retsim opened 4 years ago

Retsim commented 4 years ago

Hi,

Why is there no feature such as moving a file and update it location in client torrent ? I'm not using post-processing features because of that.

We are given the choices to use symlinks, hardlinks, and copy to keep seeding. Moving torrents does not allow to keep seeding as it breaks the torrent location. Also, I tried hard and soft links, but it didn't seemed to work well on deluge for me, ended making scripts to clean-up all the created links.

Finally, some people don't want to polluate their system with hundred various links.

There is an option "move on completed" we can already set, I use it to have a temp directory and a clean "downloaded" directory, this is working well with my client (deluge).

Deluge also have a "move storage" options, why is it not used ? By using it, I may be able to profit of post-processing:

1/ Medusa add torrent to deluge with "move completed" options, to the final "downloaded" directory. (already available)

2/ Medusa Post-Processing activated on a "move torrent storage" mode: It looks up the "downloaded" directory for new files, and instead of simple moving/copying/linking, in our structures (/postprocessed/serie/season/episode).

It uses the "move storage" option from deluge RPC, setting the target path. That way, there would be no place consumed (copy), no links created, keeping seeding on.

(There may already asked before (didn't found), and there is maybe technical reasons to not do so.)

Thanks :)

thenamelessthing commented 4 years ago

Following, I have the same problem!