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!

The one actual use I’ve found people say they use it for is people who don’t want to expose the web interface to interact with their Servarrs and only interact via SSH. Then they like to use this instead.

Sorry for the confusion! I was trying to be a little cheeky and I guess I didn’t realize how that may come across!

I saw that the PR was merged. Let me know when it’s available and I’ll add the nix-env -i managarr to the README

Thanks for doing the legwork on this! I would definitely be a bit out of my depth on that PR without actually having Nix installed 😂.

Once it’s merged I’ll update the README to mention the Nix installation method.

Sounds good, let me know! Also give me some links to track it too so I can also add it to the repo!

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?

Did you happen to have a GitHub action to go with this too? Turns out that refactor took a lot less time than I expected.

Oh and that next release is going to be a minute. I realized a massive race condition bug between the networking thread and event thread that I want to resolve. It’s going to take a minute since I’m going to have to move a good amount of logic from the networking thread to the even thread to send parameters to the networking channel. So the next patch will be that fix, the release fix, and the dynamic UI based on the config. If you want, I can ping you when I’m going to do it so you can open your MR and we can get the Nix package into the next release.

That was literally going to be one of the things I was going to ask someone to help me out to do. I wanted to make it available for Nix as well so I have no idea how to write a package definition for it, though I’m sure I could figure it out. I’m seriously stoked you did that! Thanks!

Thanks for pointing out the tagging bug. I just pushed out the fix to the release pipeline to correct that.

As for the configuration, it’s quite funny you mention that because I just earlier today pushed out the fix for that and I plan to have it as part of the next release. The fix being, that the UI dynamically changes based on what Servarrs you have in your config file.

And as for the color theme, that’s an interesting thought. I’ll look into it now!

Thanks for the feedback, I really appreciate it. And seriously, thanks for catching that tagging bug. That’s definitely not ideal…

Thank you so much! I was wondering if anyone had been using it more consistently because I was waiting for more bug reports to come in but haven’t yet. I started thinking, "There’s no way I didn’t miss something. I gotta figure out how to break it! 😂

I’m so glad you like it and use it!

Thank you I appreciate it! ☺️

Thank you so much! ☺️

I just made the repo public! So here’s a link to the Managarr repo, and here’s a link to my personal Wekan board to track my progress towards the alpha-release goal.

Wow! I wasn’t expecting such a positive response! Thank you so much!

I hadn’t made the repo public yet because I’m still working towards getting the project into a state that I would consider fully ready for contributions. This means things like CI/CD, contribution guidelines, release pipelines, better developer experience through all of this automation, etc.

But given the overwhelming response to, I guess, the initial “announcement” that it even exists, I don’t see any reason why to not just make the project public while I work towards that alpha release goal.

So here’s a link to the Managarr repo, and here’s a link to my personal Wekan board to track my progress towards the alpha release goal, where I’ll consider the project fully ready for contributions.

Haven’t told this to anyone yet, but you did say “half baked”!

Similar to the idea behind k9s, I’ve been building a rust-based TUI to manage all your standard . I’m calling it Managarr.

I’ve been working on it since January and I’m almost done with just the Radarr support, allowing you to add/edit/remove movies, indexers, collections, root folders, etc, view logs, tasks, updates, things like that. And you can view specific movie info and do manual searches, trigger searches, add/remove tags, etc.

The only big things left are

• Finishing the UI for editing indexers and adding them (to support use cases without Prowlarr)
• Support modifying quality definitions
• Add sorting functionalities to the library and collections tables
• Building mock servers for Transmission and Nzbget so I can create a docker container for users to test and play with before they install anything.

Here’s a few screenshots:

Once I’m back to not being constantly busy with work, I’m hoping to push this thing across the finish line and get it into alpha and implement all the usual stuff like license, contribution guidelines, CI/CD, release pipelines, adding it to the standard package managers, etc.