I was recently furloughed from work, so in between job applications, I decided to polish off Sonarr support in my Managarr TUI. Thus, I’m very proud to announce the beta release of Managarr with Sonarr support!
TL;DR: Managarr is a TUI and CLI for managing your Servarr instances. As of now, it now supports both Radarr and Sonarr and all the features that are available in the UI are also available in the CLI for scripting and additional automation.
The new version has the following features:
- Wider platform support (Windows, Mac, Linux, x86_64 and arm64)
- View your library, downloads, blocklist, episodes
- View details of a specific series, or episode including description, history, downloaded file info, or the credits
- View your host and security configs from the CLI to programmatically fetch the API token, among other settings
- Search your library
- Add series to your library
- Delete series, downloads, indexers, root folders, and episode files
- Trigger automatic searches for series, seasons, or episodes
- Trigger refresh and disk scan for series and downloads
- Manually search for series, seasons, or episodes
- Edit your series and indexers
- Manage your tags
- Manage your root folders
- Manage your blocklist
- View and browse logs, tasks, events queues, and updates
- Manually trigger scheduled tasks
- Manually trigger scheduled tasks
- And more!
Here’s some screenshots of the Sonarr tab:
Thanks to everyone’s feedback when I first posted the alpha release here, this version sports a handful of additional performance improvements and platform support.
This is now technically in beta, so if anyone encounters any issues, please let me know!
No, but I will try to incorporate the nixpkgs update script into it now that the metadata is fixed for the release. I’m not a nixpkgs maintainer (yet) though but usually this is close to automatic.
If you want, you can also submit and maintain the package, or I can put us both as maintainers
Given that I can’t really see what would change in Managarr that would require additional changes in the Nix package, I see no reason not to have us both as maintainers, especially since I don’t currently have Nix installed. (It’s high up on my to-do list, don’t worry! I know I’ll like it!)
Are there any files that would need to be checked into the repo so we can maintain an official package for it?
No,
Cargo.lock
is the only relevant optional one for Rust packages and that is already there, so we should be good. I’ll request it tomorrow if someone else doesn’t beat me to it ;)Sounds good, let me know! Also give me some links to track it too so I can also add it to the repo!