the *arr family (Sonarr, Radarr, Lidarr and Readarr) + Jackett
-
- Sonarr: Smart PVR for newsgroup and bittorrent users. https://sonarr.tv
- Radarr: a fork of Sonarr to work with movies à la Couchpotato. https://radarr.video
- Lidarr: Looks and smells like Sonarr but made for music. http://lidarr.audio/
- Readarr: Book, Magazine, Comics Ebook and Audiobook Manager and Automation (Sonarr for Ebooks)
and their cousin
- Jackett: API Support for your favorite torrent trackers.
Basically, Jackett relay your queries between Sonarr, Radarr, and Lidarr to Torrents and Newgroups than send it to your favorite Torrent Client such as (Transmission, qBittorrent,...) than Sonarr, Radarr, and Lidarr are noticed when the download is done and/or you watched it with Jellyfin or Plex.
The trick is to have a shared storage where all these apps have access to maintain meta data, such as I was trying to explain here: @JOduMonT said in Gerbera a UPnP Media Server:
it's yunohost had a hard time with shared and personal data and nextcloud
-
I note that Cloudbox packages all these up and more.
-
The following packages work for the *arr family:
- Sonarr: https://git.rohitja.in/rohit/sonarr-app
- Radarr: https://git.rohitja.in/rohit/radarr-app
- Lidarr: https://git.rohitja.in/rohit/lidarr-app
- Bazarr: https://git.rohitja.in/rohit/bazarr-app
- Jackett: https://git.rohitja.in/rohit/jackett-app
Readarr does not have a community docker image at this time, besides still being under development to my knowledge.
Of course, all these are very unpolished, and non-optimal and, imho, not ready for general use yet. Besides the servarrs being all beta v3, the docker image also does things like using mono instead of .net core. There are redundant steps in the recipe too, I am sure. The docker layers are also not handled optimally to increase layer re-use. Still, they might provide a starting point; and for anyone who wants to play around with the tools.
-
I wonder if @girish you ever had time to look into this? Would be great to have Radarr as a Couch Potato replacement (since the latter has not been maintained since 2015)
-
@avatar1024 Not yet, no.
@esawtooth Have you been using the apps actively? Do they work well and what's the status of the packages?
-
-
@esawtooth the packages dont seem to be working any longer
-
@girish is support for these apps planned? Will they be published?
-
@Trackborne Not immediately, maybe when we find a bit more time. Some of these apps are a bit complicated to 'support' for piracy reasons.