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!
You must log in or register to comment.
I use docker for my *arr stack. I’ve never had any problems just logging into radarr and sonarr to check what media I have and its stats.
Tell me:
Why should I use this?
What advantages does this give me over using each service’s GUI?
Is there any plan for a GUI?
Is this a substitute for something else you felt did not do enough?
What modifications are needed for integration with docker containers?
To answer your question, I built it for a few reasons:
- I wanted to learn Rust, so I used this project to do that
- I really love TUI’s and I pretty much live in my command line at work, and since I already automate everything I can to make my work life easier, I wanted to be able to do the same with my homelab
- I think it looks cool
- For fun. If no one else ever gets use out of it, that’s okay! I just really enjoyed building it and I’m excited to build out more of it.
But also: Why not?
So really, you would only use this if you like TUIs or want a command line tool for interacting with your Servarrs. If you have no use for it, that’s totally fine too!
As for container support: if you mean if there’s a docker version, yes there is. If that’s not what you meant, then my bad!
I wanted to learn (…)
Well, you make the finest point
Thank you for answering. I will research some more to see how well it works with my setup.
Thanks for all your work!
Thank you for the feedback. I appreciate you!
I think it’s a great idea, as it also gives you access to your *arr stack from a simple ssh session, so you don’t have to expose the GUI interfaces to the Internet!
Well done! I’m looking forward to playing with this!
Thanks!
Thank you so much! I really hope it lives up to the hype it’s getting 😅
Sometimes people build things just because they want to. Some people will take a look and say “hey that’s cool” and use it. Some others will take a look and say “this does nothing for me” and both are valid opinions to have. IMO nobody should have to justify an open source project unless asking for funding.
I find using mouse clumsy and welcome a TUI interface. If you like GUI better, stick to using it and don’t shit on OP’s work