![deluge torrent consore deluge torrent consore](https://www.stemjar.com/wp-content/uploads/2017/12/deluge-review-696x432.png)
Show information about the disk cache Usage: cache p PATH, -path=PATH save path for torrent Help commands can be displayed for each command using the -help flag.
![deluge torrent consore deluge torrent consore](https://img.creativemark.co.uk/uploads/images/906/10906/largeImg.png)
Deluge torrent consore how to#
It always thinks /downloads/downloading should be c:/downloads/downloading, not sure how to get around that yet.Deluge Console Documentation Start the console interfaceĬonnect to your daemon (Replace # with your Deluge daemon port found on your slot info page): connect 127.0.0.1:# I've been trying but I can't get it to work with the path command yet, unfortunately.
Deluge torrent consore password#
Parameters: connect IP:PORT USERNAME PASSWORD add -p \"\downloads\downloading\Golden Kamuy\" \"C:\Users\user\AppData\Roaming\Taiga\data\feed\bnlhYS5zaQ=\ Golden Kamuy - 13. Parameters: add -p \"\downloads\downloading\Golden Kamuy\" \"C:\Users\user\AppData\Roaming\Taiga\data\feed\bnlhYS5zaQ=\ Golden Kamuy - 13. Based on the layout of the arguments I don't think it should be too difficult because it seems like the biggest difference would be adding the ip, port, username and password before the "add" arguments: I think at this point for this to be fully supported under taiga, there needs to be a section in the Torrents category where we can add the NAS connection info and so it can pass those arguments in the parameter. I tried to blur out my name and password though. Double-checking on my NAS, it is also working there. I got it working with the commands I mentioned at the end of my post. Instead of editing I'll just add this separately. I need to figure out how to actually do these commands first before I can try testing it myself though.
Deluge torrent consore Pc#
That's just my laymans understanding, but if deluge-console were connecting to the daemon and adding the torrent that way, I think it should be possible to have the torrent start on the NAS while using the gtk UI on a PC to connect to it. That said, looking at their wiki at ), it seems it may be possible if deluge console were connecting to to the NAS daemon, I think the arguments would need to be accessible through Taiga for that to be possible though. I noticed even though it wasn't making torrents, it was still making a directory on my c drive (C:\downloads\downloading\Golden Kamuy), so it's probably just the way deluge-console works. It seems like its probably due to deluge more than taiga to be honest. I'm guessing deluge console always treats the file path like a local filepath, maybe? I figure I might just have to settle for running taiga downloads off my PC and using the network path to the NAS. Seems like on the NAS path it times out right away. => Request header | GET /download/1082330.torrent HTTP/1.1 17:44:36 http_callback.cpp:126 base::http::Client::DebugHandler | Re-using existing connection! (#0) with host nyaa.si 17:44:36 http_callback.cpp:126 base::http::Client::DebugHandler | Found bundle for host nyaa.si: 0x5348080 17:44:36 http_request.cpp:101 base::http::Client::SetRequestOptions | URL:
![deluge torrent consore deluge torrent consore](https://www.tipsandtrics.com/img/linux/298/deluge-an-awesome-unappreciated-cross-platform-bittorrent-client-4.png)
Reusing client with the ID: taiga-http-0000000005 17:44:36 http.cpp:431 taiga::HttpManager::ProcessQueue | Connections for hostname is now 1: nyaa.si 17:44:21 http.cpp:461 taiga::HttpManager::FreeConnection | Connections for hostname is now 0: nyaa.si Parameters: add -p \"\\Tartarus\anime\test\Golden Kamuy\" \"C:\Users\directory\AppData\Roaming\Taiga\data\feed\bnlhYS5zaQ=\ Golden Kamuy - 13. Tried under local client with a network path to the NAS though, and that works: Tried both ways, slightly different log errors but neither would add a torrent to deluge. I used /downloads/downloading as my path because that is the mount path for deluge on my NAS ( ). 17:41:56 file_monitor.cpp:184 DirectoryMonitor::MonitorProc | Stopped monitoring. 17:41:53 http.cpp:461 taiga::HttpManager::FreeConnection | Connections for hostname is now 0: nyaa.si \"C:\Users\directory\AppData\Roaming\Taiga\data\feed\bnlhYS5zaQ=\ Golden Kamuy - 13. Parameters: add -p \"\downloads\downloading\Golden Kamuy\" 17:41:53 feed_aggregator.cpp:397 Aggregator::HandleFeedDownloadOpen | >Īpplication: C:\Program Files (x86)\Deluge\deluge-console.exe