I got Jellyfin up and running, it’s 10/10. I love this thing, and it reinvigorated my love for watching movies. So I decided to tackle all the other services I wanted, starting with Paperless-ngx…

What a nightmare. It doesn’t have a Windows install so I made an Ubuntu VM. Don’t get me started on Ubuntu. I just spent about 12hrs trying to get Portainer to cooperate and had to give up. I tried just installing Paperless the “normal way” and had to give up on that too.

My point: if you’re getting started selfhosting you have to embrace and accept the self-inflicted punishment. Good luck everybody, I don’t know if I can keep choosing to get disappointed.

Edit: good news! Almost everything I wanted to do is covered by Jellyfin which can be done in Windows.

        • towerful@programming.dev
          link
          fedilink
          English
          arrow-up
          3
          arrow-down
          1
          ·
          1 year ago

          If you have a spare computer, install proxmox on it.
          There are loads of tutorials how to do this, it has a good installer, after which it’s all a web based GUI.
          Use it to spin up VMs to your heart’s content, create scripts to automatically provision a new Ubuntu or Debian or whatever flavour. Or run up some Windows VMs. You can pass through GPUs and other devices (tho this can be difficult, again lots of tutorials out there).

          Be prepared to spend some time learning proxmox. It took me 2 or 3 installs to figure out the best way to set up networks, storage etc. Mostly cause I just jumped in, found something that could be better, googled that and found a useful tutorial on it so started again.
          But once proxmox is running, everything else become so much easier

          • Chewy@discuss.tchncs.de
            link
            fedilink
            English
            arrow-up
            2
            ·
            1 year ago

            I don’t think proxmox is great if you don’t know Linux yet. It’s an additional tool to understand. But I do regret not getting into proxmox earlier, since it makes trying new things so much easier.

    • Cyclohexane@lemmy.ml
      link
      fedilink
      English
      arrow-up
      8
      ·
      1 year ago

      Windows is just not ready for this stuff. Most of this stuff is built for Linux. Linux is THE server OS. And windows is painful for developers too, so there’s less solutions for it.

      You’ll be a lot better off with Linux for self hosting.

      • LazerDickMcCheese@sh.itjust.worksOP
        link
        fedilink
        English
        arrow-up
        0
        ·
        edit-2
        1 year ago

        I’ve got Docker up and running, but getting anything to work within Docker or getting a machine to access the services that it says are running is a different story

        • cestvrai@lemm.ee
          link
          fedilink
          English
          arrow-up
          3
          ·
          1 year ago

          I have worked with Docker/WSL for a number of years and it is more difficult compared to Docker in Linux. There are a lot a unique quirks and bugs that are an absolute pain to deal with.

          Would not recommend for any relatively complex use case and certainly not for a server.

        • Chewy@discuss.tchncs.de
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          This sounds like ports aren’t forwarded correctly. At least that’s a regular problem I have. ss -tunlp shows which ports are open and helps me often to find out if I’m just too dumb again ;D

          I do think that if you continue to set up services on Linux (with or without docker), you’ll get quickly to a point where setting up a new service takes only a few minutes.