Repository navigation
Add “Open location” using remote-to-local path mapping #2079
Replies: 1 comment 1 reply
Already available: External Programs qui already has remote-to-local path mapping plus a torrent context-menu action that launches a program with the mapped path. Configure it under Settings → External Programs → Create External Program:
Then right-click a torrent and pick your entry under External Programs. Mappings resolve longest-prefix-first, as you suggested. Where the behavior differs from your list: when no mapping matches, qui passes the original path through instead of raising an error. One constraint worth stating: external programs run on the machine that hosts the qui backend, not in the browser. This setup works when you run qui itself on the Windows box with the NAS share mounted. If the qui backend runs on the NAS, nothing it launches can open Explorer on your desktop, because a web page cannot start a program on the client machine. |
Uh oh!
There was an error while loading. Please reload this page.
Feature request
qBittorrent WebUI clients usually cannot support an Open location action in the same way the desktop client can, because the qBittorrent backend often runs remotely, for example in Docker on a NAS. In that setup, the torrent path returned by qBittorrent is a server-side path, not a path that exists directly on the machine running the WebUI/client.
Qui could solve this by allowing users to manually map remote download paths to local/network paths on the client machine.
Example:
If a torrent is located at:
Qui would translate it to:
and open that location in Windows Explorer.
This would be useful for users who run qBittorrent on a NAS/server but use Qui on Windows with the NAS folders mounted as network drives or SMB shares.
Suggested behavior:
This could also work on Linux/macOS by mapping remote paths to local mount points.
All reactions