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!

  • Dark-Alex-17@lemmy.worldOP
    link
    fedilink
    English
    arrow-up
    1
    ·
    8 days ago

    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!

    • Laser@feddit.org
      link
      fedilink
      arrow-up
      1
      ·
      8 days ago

      It’s rather simple in good cases, here’s my version:

      {
        lib,
        fetchFromGitHub,
        rustPlatform,
        perl,
      }:
      
      let
        pname = "managarr";
        version = "0.4.1";
      in
      
      rustPlatform.buildRustPackage {
        inherit pname version;
        src = fetchFromGitHub {
          owner = "Dark-Alex-17";
          repo = pname;
          rev = "df9bba32cb1628fe0bdf33c71089d7ae085066d4";
          hash = "sha256-2KWuqv0nxMc+H+lmuNQ0lbEm5yE2akuZTa7PT5JcvBs=";
        };
      
        cargoHash = "sha256-hB4uRgVUp6YngMoXqd03U/n+HdlcYdL5bwvTxI4xCLE=";
      
        nativeBuildInputs = [ perl ];
      
        meta = {
          description = "A TUI and CLI to manage your Servarrs";
          homepage = "https://github.com/Dark-Alex-17/managarr";
          license = lib.licenses.mit;
          maintainers = [ ];
        };
      }
      
      • Dark-Alex-17@lemmy.worldOP
        link
        fedilink
        English
        arrow-up
        1
        ·
        7 days ago

        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.

        • Laser@feddit.org
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          6 days ago

          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

          • Dark-Alex-17@lemmy.worldOP
            link
            fedilink
            English
            arrow-up
            1
            ·
            6 days ago

            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?

            • Laser@feddit.org
              link
              fedilink
              arrow-up
              1
              ·
              6 days ago

              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 ;)

                  • Dark-Alex-17@lemmy.worldOP
                    link
                    fedilink
                    English
                    arrow-up
                    1
                    ·
                    4 days ago

                    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.