Going to have to fire up the pirate ship now.

    • propter_hog [any, any]@hexbear.net
      link
      fedilink
      English
      arrow-up
      6
      ·
      8 months ago

      I would love a writeup. I have a seedbox on Ultra and it’s just sitting there doing nothing because I’m too stupid to know how to set any of this shit up.

    • please do. I have been working my way through setting it up on a dedicated Ubuntu machine. I’ve got my software installed, jellyfin is rolling with my existing library which is now like 99% curated/accurate and now I’m just trying to figure out if I need to / how to containerize qbittorrent to only work over the VPN (and to close with no leaks if that tunnel drops).

      the whole container thing is new to me and kinda confusing. when I did this in windoze, there was a setting in qbittorrent to just do this… though obviously in windoze I was doing it all manually, and now I’m trying to set up an automated piracy box lol.

      I’ve learned a lot in the past two weeks of doing this, but I’m at the threshold between “cool setup” to “I am a self-hosted media warlock”. I am so close, I can taste the power in the air. haha

        • Baaahb@feddit.nl
          link
          fedilink
          English
          arrow-up
          3
          ·
          edit-2
          8 months ago

          Home assistant really benefits from being run as an OS. RaspPI or similar would legit be my recommendation.

          For a media server though, I learned mostly by starting with these two repos: https://github.com/geekau/mediastack https://github.com/SimpleHomelab/Docker-Traefik

          Both will get you where you want to go. Simple homelab is a much cleaner setup if you actually want to run a server as the compose is separated out into individual includes per container/stack, but is way overkill for your use case, even though the documentation should make it reasonably simple to adapt. Media stack does exactly what you are trying, but the organization of the server isnt as nice, and the associated documentation may be over your head. Its definitely over mine, but I’m a “poke it rill it works” guy and not a “just read the damn instructions” guy.

        • fair enough. containerization certainly did not come across as intuitive, even going through the docker tutorials. I try to be patient with myself at learning new shit, and even now I still am baffled.

          as with all things computer, after rambling about my problem in here, it gave me an idea and now I think I have the binding configured in qbitt… so now I’m onto setting up accounts/group permissions for radarr and sonarr.

          I’m trying not to rush myself and to use “best practices” instead of like “dirty” strategies, like making everything root. also, I take lots of “done for the day” breaks with this project to keep from getting frustrated and taking a big swing out of impatience.

          i am super excited for the quality profiles to kick in and start upgrading my existing library. I’ve been at this for so long, I have lots of stuff that is 480p. I’m gonna have to configure some kind of “do this at night only” guardrails for a while once it’s going. I’m setting it up for minimum 1080p.

          also prob gonna have to start working my way into some private trackers once my weak shit runs dry.