I used Jackett until I had to transfer some split up programs to the same machine. Some indexers needed Flaresolverr but it was broken, because my version of Jackett was a service install instead of docker. Anyway it made sense to switch to Prowlarr because I already use Sonarr and Radarr
Jackett can be run on any computer. It doesn’t need a server or any serious hardware. It can probably be run on a $20 Pi. It’s just allows you to interact with trackers via API calls.
I use Prowlarr via Docker now a days. It’s provides a much better experience to interact with othe instances of ARRs.
Why do this instead of Jackett?
Jackett is one of the included plugins. I recently set it up on my machine alongside the other plugins as well.
Jackett I think is a better solution. There is a crazy amount of sources to search/select from and setting up the API key is just editing a file.
I used Jackett until I had to transfer some split up programs to the same machine. Some indexers needed Flaresolverr but it was broken, because my version of Jackett was a service install instead of docker. Anyway it made sense to switch to Prowlarr because I already use Sonarr and Radarr
Isn’t jackett like a server thing?
Jackett can be run on any computer. It doesn’t need a server or any serious hardware. It can probably be run on a $20 Pi. It’s just allows you to interact with trackers via API calls.
I use Prowlarr via Docker now a days. It’s provides a much better experience to interact with othe instances of ARRs.
Ohh server I meant it has to be run on boot so some laymen just prefer qbit search.
No