What does download_in_external_client actually do?

[balkce]

I've tested torrra with download_in_external_client set to true and false, and it seems that in both cases torrra handles the download process throught is own torrent function. Am I missing something?

Here is my configuration:

[general]
download_path = "/disks/Torrents"
download_in_external_client = true  #WHAT DOES THIS DO?
theme = "textual-ansi"
use_cache = true
cache_ttl = 300
seed_ratio = 3.0

[indexers]
default = "prowlarr"

[indexers.prowlarr]
url = "http://localhost:9696"
api_key = "blahblahblah"

I have my own torrent downloader (Tranmission), and Prowlarr is able to communicate to it without issues. Is there a way for torrra to 'connect' to it like Prowlarr does?

[stabldev]

hi, sorry for the confusion. i released a fix on v2.0.1.

well, here is what download_in_external_client flag does,
if youve set it to true, torrra doesnt handle it internally, it simply calls webbrowser.open(). this hands the magnet uri over to the OS/browser, which then opens it in whatever the applications is registered as the system default magnet: handler.
this works great for qbittorrent, transmission (GTK/Qt) as long as they are configured as the default handler, if not; it will show some kinda popup to select.

here i assume you;re using transmission daemon with web ui.
transission in headless mode doesnt register itself as the default system-level magnet handler.
it relies entirely on its RPC API.
Torrra doesnt support the transmission RPC interface yet.

this is definitely a useful feature, i'll try to implement it in a future release.
and nothing wrong with your config file :D
thank you!

[balkce]

This has been followed up in #192