I just started to selfhosting services and want to try with the *Arr ecosystem. What newbie tutorial recomend for start with it?

I am currently learning by deploying docker containers in rpi5

Thanks for your time and patience

  • jws_shadotak@sh.itjust.worksEnglish
    10·
    1 year ago

    I don’t really have a tutorial suggestion but this is a great resource if you haven’t seen it yet:
    https://wiki.servarr.com/

    I would also recommend using dockge to help create and manage your stacks.

    When you’re setting up the services, go through each section and take note of what you don’t understand. The services tie into each other so it may be beneficial to set up your stack first (docker compose YAML text file, managed by dockge) and configure stuff together.

    • leaf@feddit.nlEnglish
      5·
      1 year ago

      Wow dockge is something I’ve wanted for a long time but didn’t know existed.

      Time to finally dump portainer.

    • Im_old@lemmy.worldEnglish
      4·
      1 year ago

      Plus1 for dockge. Started using yesterday (with podman), moving from portainer (with docker). And I have around 50 stacks, so not just a few *arr. It’s really good, and the option to work directly via CLI or the web interface is really nice!

    • Lumilias@pawb.socialEnglish
      3·
      1 year ago

      And miss out on all the struggle and suffering of figuring out how to build a compose file over many hours? Who would want to miss out on that?

      All kidding aside, I had not heard about dockge. I might give it a try, see what it can do with my existing compose file.

    • LoboAureo@lemm.eeOPEnglish
      1·
      1 year ago

      Currently I’m using casaOS that does the deployment automatically. I installed portainer to have more control of the containers.

      I’m going to read both links. Thanks!!

    • ares35@kbin.social
      2·
      1 year ago

      have several systems and vm (all x64, don’t have any sbc here) running dietpi. love it.

      saw https://runtipi.io/ posted elsewhere recently. which essentially results in the same thing, but is based on docker.

      • AverageGoob@lemmy.worldEnglish
        1·
        1 year ago

        Huh I have been meaning to try working with docker so this seems like a good starting point! Thanks for sharing.