Repository navigation
[FR] Migrate torrent(s) to another (local) client #954
Replies: 9 comments
|
Would appreciate this as well |
|
+1 |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
This appears to be related to:
These requests all involve moving/sending torrents between qBittorrent instances. |
|
As mentioned in another post i got a POC working in PR #1253 . Is still in development but I think it shouldn't be that hard. I hope I'll get around to polish it a bit in the next days and then we'll see how it turns out :) |
|
I realized that it is possible to preserve all torrent data (except trackers added manually) if using fastresume files by copying the associated files in BT_Backup to the new instance. |
|
You can do this with automations. |
|
@0rkag's PR #1253 has since been closed. PR #1736 has since been merged, which I assume followed the philosophy of feature request #1126 that looked for a way to transfer torrents from an external seedbox to a local client. It's a bit of a different problem; local-to-local of course has all the data already available locally and only needs to know where the user wants it to end up, while external-to-local raises the question of having to include a file transfer utility or assume the data is already present, and I feel needs a lot more variables from the user so the decision to implement this as an automation makes a lot of sense. For local-to-local however I am still very much on board with the original feature request of having this an option in the torrent context menu. I guess with the automation PR being merged the backbone of it has already been implemented anyway. I hope any dev reading this thread can reconsider this request as not being fully implemented yet and a viable addition to qui. What is a hard requirement for me though is no data being lost in the move (such as add date, upload and download), which I assume is as simple as moving both the .torrent and .fastresume files. I'm not sure if the automation includes that already. |
Agent Brief Category: enhancement Current behavior: Desired behavior: Key interfaces:
Acceptance criteria:
Out of scope:
Why a human: Whether a manual twin of the Export to Instance automation action belongs in the torrent context menu is a scope call, and so is where it lives in the UI. The thread also asks that a move keep the added date and the transfer totals, which the WebAPI add path cannot carry. Preserving them means writing fastresume files into the session directory of the target while both clients are stopped, which is a second mechanism with its own filesystem access and safety requirements, and that is a maintainer decision. |
Uh oh!
There was an error while loading. Please reload this page.
Is your feature request related to a problem? Please describe.
It would be cool to be able to migrate torrents to another client, like moving all cross-seeds to a dedicated torrent client
Describe the solution you'd like
A "Migrate" button, when selection one or many torrents, it would then stop the torrent(s), migrate them over to the new client, then start the torrent on the new client, and give the option to remove the torrent(s) on the old client
Or instead of a migrate button on the context menu, it has a dedicated tab (under settings), called, extra tools, where one of the tools, migration, you can do the it based on torrent client + matching category AND/OR tags
Describe alternatives you've considered
the manual way of copying over the .torrent files and .fastreume files into the BT_Backup(Qbittorrent) of the new client, but without the torrent API to name give of the torrent, its hard to know which ones to copy
Additional context
you may need to stop and restart both qbittorrent clients during the process
Also the torrent clients would both use the same /data structure (an ideal hyperlinking setup), and the torrent clients have their own ports and config folder, and Qui has RW access to the config folders
All reactions