• grue@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          ·
          20 days ago

          IMO the trouble is that there are so many of the things now that I need a damn flowchart to understand how they work together and which ones I need.

          (No, seriously: I want to set up an *arr stack but don’t understand how. Could somebody please send me a flowchart??)

          • Vendetta9076@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            0
            ·
            19 days ago

            All you actually need are sonarr (tv) radarr (movies) overseer (request management) and prowlarr (indexer management) you don’t actually need the last two.

          • cerothem@lemmy.ca
            link
            fedilink
            English
            arrow-up
            0
            ·
            19 days ago

            Here’s a very old flow chart I made for some folks that didn’t want to use Linux. Though it mostly applies to any serup

          • DesolateMood@lemmy.zip
            link
            fedilink
            English
            arrow-up
            0
            ·
            19 days ago

            For the purposes of this explanation sonarr and radarr are the same, but keep in mind that sonarr only does tv shows and radarr only does movies

            You tell sonarr what you want to watch --> sonarr tells prowlarr what you want to watch --> prowlarr will search websites for magnet links to your show (you have to specify which websites) --> prowlarr will give the download manager (qbittorrent, etc) the magnet link and it will download it --> sonarr will take the downloaded file and copy it somewhere else for organizational purposes --> media server (jellyfin) will see the copied file and download associated metadata (thumbnail, episode name, episode number, etc) and allow you to watch it

            The only programs you need for a purely functional arr stack are sonarr/radarr, prowlarr, qbittorrent, and jellyfin, or any other media server. Anything else is purely icing on the cake

    • mlg@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      19 days ago

      There’s more *arr tools that aren’t aggregator automation tools than there are aggregator automation tools.

      Also It was only funny when using an existing words like "sonar, “radar”, “lidar”. Jellyseerr is dumb, even Jackett was pushing it.

      I guess it makes it somewhat easier to associate them as part of a group of software, but now we have stuff like Homarr that is entirely unrelated, but still a useful tool.

      • augustus672@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        19 days ago

        To be fair, jellyseerr is a fork of overseerr focused on jellyfin, so the name at least makes sense.

    • Pycorax@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      19 days ago

      I mean it is clear that it’s an aggregator (? Not sure what the right term is for this) but I can’t even begin to count the number of times I access Radarr instead of Sonarr because I forgot which one is for shows or movies.

      Prowlarr is way more intuitive at least.