241

After almost 3 years of work, I've finally managed to get this project stable enough to release an alpha version!

I'm proud to present Managarr - A TUI and CLI for managing your Servarr instances! At the moment, the alpha version only supports Radarr.

Not all features are implemented for the alpha version, like managing quality profiles or quality definitions, etc.

Here's some screenshots of the TUI:

Additionally, you can use it as a CLI for Radarr; For example, to search for a new film:

managarr radarr search-new-movie --query "star wars"

Or you can add a new movie by its TMDB ID:

managarr radarr add movie --tmdb-id 1895 --root-folder-path /nfs/movies --quality-profile-id 1

All features available in the TUI are also available via the CLI.

you are viewing a single comment's thread
view the rest of the comments
[-] Voroxpete@sh.itjust.works 16 points 2 days ago

I'll admit, as neat as this is, I'm a little unclear on the use case? Are there really situations where it's easier to get a command prompt than it is to open a webpage?

The CLI side I can see more use for since that does expose a lot of actions to bash scripting, which could be neat. But on the whole I can't say I've ever really found myself thinking "Man, I really wish I had a UI for managing Radarr, a program that already includes a really good UI."

I know it's shitty to hate on something just because you're not the target for it. That's not my intent, it's more that I'm just fascinated by the question of how anyone has a burning need for this? It feels like there must be something I'm missing here.

[-] aclarke@lemmy.world 3 points 19 hours ago

No hate perceived on my end! 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?

[-] Voroxpete@sh.itjust.works 3 points 17 hours ago

Well, can't say fairer than that.

[-] killabeezio@lemm.ee 1 points 1 day ago

Does there need to be a need? Some people just like to create things to see if they can. Some people like TUIs. There may not be a huge need for this, but it's pretty freaking awesome to have.

[-] Voroxpete@sh.itjust.works 2 points 23 hours ago

Yeah, I did try to stress that just because I can't envision a use for it, doesn't mean it shouldn't exist. I'm totally OK with that. My question was more "Am I the idiot here for not being able to see what the use is?"

[-] killabeezio@lemm.ee 2 points 22 hours ago

I know what you mean. There are tools I see everyday and I ask, but why? I have started to just ask, why not? There doesn't always have to be a use case and sometimes people just want to create shit. They don't even care if others use it, but want to share it anyway in case there is that one other person that does.

[-] choco@sh.itjust.works 7 points 2 days ago

Could be really useful to have a UI over SSH without opening your web interface to the world. I will try because it seems great for my use case !

[-] Voroxpete@sh.itjust.works 6 points 2 days ago

But that implies you do have your SSH open to the world, right?

The way I access my private web interfaces remotely is through something like Netmaker, Tailscale or Zerotier. Same thing for SSH. No way in hell am I opening 22 on my router.

[-] choco@sh.itjust.works 1 points 1 day ago

You are not wrong, most of the time I SSH from the same IP so I only have 22 open from this adress. I think I just prefer managing this one access protected by a big key without thinking about my reverse proxy, plus I think TUI are neat. But objectively you are right, there may not be a lot of advantages.

Thanks to the developers though, I always appreciate such hard work and sharing to the community ♥️

[-] Revan343@lemmy.ca 0 points 1 day ago

You can use any port for ssh. When I switched from 22 to 1337, brute force attempts at logging in stopped

[-] Voroxpete@sh.itjust.works 2 points 1 day ago

Obscurity is not the same thing as security.

[-] Revan343@lemmy.ca 1 points 15 hours ago

Well I use key-based login for security; obscurity just keeps the network congestion down

[-] ShortN0te@lemmy.ml -4 points 1 day ago

Netmaker, Tailscale or Zerotier

No way in hell i am giving a company complete remote access to my servers and clients.

[-] DesolateMood@lemm.ee 6 points 1 day ago

All these companies do is make it easier to use wireguard, if you're so afraid of them just use wireguard yourself, you'll get the same effect

[-] ShortN0te@lemmy.ml -1 points 1 day ago

This is not really correct. Those companies take complete control of the secret keys. And no, it is not the same effect when you use tailscale compared to wireguard cause of various reasons. CGNAT, no port forwarding, funnels etc.

[-] Voroxpete@sh.itjust.works 3 points 1 day ago* (last edited 1 day ago)

You know those can be self hosted, right?

And yes, by all means just set up your own Wireguard or OpenVPN access if that's what you prefer. You do you bud.

[-] Takumidesh@lemmy.world 2 points 2 days ago

Cli doesn't make much sense to me either when the *arr suite has a well documented rest API already.

this post was submitted on 31 Oct 2024
241 points (98.8% liked)

Selfhosted

39677 readers
460 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS