I looked for this info but didn’t really see a thread about it, if there is one, a link is sufficient :)

I have a win 11 off-shelf mediocre pc for my Plex/jellyfin servers (basically nothing else on that pc; it also functions as a playback device, but it has all the libraries on it so does not matter at all how I access them) and fuck windows and stuff… it was a temporary replacement for my mobo-dead Ubuntu tower, but knowing more things than I did back then, I don’t want to ‘buntu either.

So I’m looking for a good stable distro with really good file management options; bulk rename with rules is a must even if it’s an additional program (built in to Ubuntu, very very nice utility for my exact use).

I’m thinking about trying pop, tbh mostly because I’ve heard of it and mostly good things, but idk if that’s good for the use case I have, and I do NOT want to distro-hop this specific computer. Whatever it gets has to be good enough to be a long-term stable choice (to the best of anyone’s knowledge), because I’m not going to change it later; that’s almost certainly too much work. I’ve tried a few Debian-based distros, and whatever Mint is (I do not like mint at all, please don’t suggest it) on a real old enterprise tower with 16 USB ports and 4gig ram (literally nothing, including antixlinux, runs well on it and I don’t really know why…). and plan to convert a laptop with touchscreen for gaming down the line, but this specific machine is not meant for change. Ever. That’s why it’s taken me 2 years to be willing to go back to Linux. Because change means a lot of work.

Edit to add: I know zero about docker. That apparently matters, and I didn’t think to mention it. It’s… probably beyond my capabilities at this point, but even if it isn’t, fucking stop, omg. Shut the fuck up about docker. I know I need to learn it eventually, but while it’s on my to-do list, I’m not there yet. And importantly, I -do not want- to have to learn docker for this relatively minor self-host project when I’ve been managing it for over a decade without docker bullshit. I am sure it’s “super easy” like all you tech bros say, but I’m not ready for that level of unnecessary complication. I don’t use docker now, I don’t really -want- it to be necessary for what I’m doing (because it isn’t necessary).

Skill level: meh? Not a total noob, learned how to split tunnel just to keep my server up while VPN was active back when that was necessary, and figured out how to solve most of the issues I had with it (fucking nvidia…). Prefer CLI for program management and GUI for everything else. Worked windows tech support dealing with sql and winservers for SaaS, but no official skills or training. Only used windows, Ubuntu, and antix for any significant time.

Bonus round: anyone who’s ever transferred Plex servers from win to Linux (insert flavor), is it actually possible to keep my collections and playlists and stuff? I haven’t really messed with my jelly stuff because nobody but me ever uses it, but Plex is sort of a thing for like a dozen people I know, as “home” users. The last time I went from windows to Linux, in 2019, nothing transferred other than the files… but my library is 30tb now, not 10, and has a lot more curation than it used to, so that’s a much bigger problem than it used to be.

  • Apathy Tree@lemmy.dbzer0.comOPEnglish
    21·
    4 months ago

    Let’s just say that I know nothing about docker and don’t plan to learn before I do this is swap (because these are both true things, and I edited the main post because everyone assumed I know docker and I absolutely don’t)

    How does that change your reply, if at all?

    • bamboo@lemm.eeEnglish
      10·
      4 months ago

      As a person who has been managing Linux servers for about a decade now, trust me that a few hours or days of learning docker now will save you weeks if not months in the future. Docker makes managing servers and dealing with updates trivial and predictable. Setting everything up in docker compose makes it easy to recover if something fails, it’s it’s self documenting because you can quickly see exactly how your applications are configured and running.

    • jws_shadotak@sh.itjust.worksEnglish
      5·
      4 months ago

      I would recommend using Docker first on the windows machine as a step in the transition. I did exactly this when I was transitioning to debian from windows. It made the official switch insanely easy because all I had to do was set up the Docker filesystem to what it already knew and it started up without any issues.

      My lessons learned:
      Keep the database on an SSD. I put mine on a HDD and it corrupted.

      • Victor@lemmy.worldEnglish
        2·
        4 months ago

        Keep the database on an SSD. I put mine on a HDD and it corrupted.

        That seems very odd to me, and a very serious bug, no? 🤨 I feel like the storage medium shouldn’t matter as long as it can keep up with data throughput (or eventually keep up, with some help with buffering via the kernel or some other mechanism).

      • Apathy Tree@lemmy.dbzer0.comOPEnglish
        11·
        4 months ago

        When you say database, do you mean the OS and the server install? That’s my current setup; ssd for OS and anything that needs installing, with hdds for the actual content.

        I’m sure docker is easier if you know it… that’s like the point, afaik, but while basic use might be easy, it’s… never ever that easy for me, something always goes wrong, which is why I haven’t bothered yet. I know I should, I know it’ll make things easier (hypothetically), but it feels like a huge undertaking for someone with no skills. I’ve been looking for a super noob friendly instruction guide, and have not found one that I can work with, tbh, without a bunch of other know-how that I don’t have. (If you know of any I’d be eternally grateful!!!)

        • jws_shadotak@sh.itjust.worksEnglish
          1·
          4 months ago

          When you say database, do you mean the OS and the server install?

          Yes, that’s what I meant. I switched my server install to a HDD because it was running on a 256 GB SSD which was running out of room.

          I’m sure docker is easier if you know it… that’s like the point, afaik, but while basic use might be easy, it’s… never ever that easy for me, something always goes wrong, which is why I haven’t bothered yet. I know I should, I know it’ll make things easier (hypothetically), but it feels like a huge undertaking for someone with no skills. I’ve been looking for a super noob friendly instruction guide, and have not found one that I can work with, tbh, without a bunch of other know-how that I don’t have. (If you know of any I’d be eternally grateful!!!)

          I can give you some tips for now and then I’ll give you some more in-depth instructions when I’m at my computer again.

          For now:
          Install Docker to your computer. I’m not sure how windows Docker handles it but I recommend using Docker compose. I’m not sure of the technical differences between Docker and Docker compose, but I found Docker compose to be much easier to use because it’s saved as a YAML file (text file). If you need to make changes, just edit the file.

          Once you have that set up, get a Plex server running. You’ll probably have to change the ports in the Docker one to avoid conflict with your current one.

          I recommend LinuxServer.io for a lot of things, including Plex. There’s some dissent over use of Linux Server’s apps due to permission and root things, but they are also super simple to use and you can start with the basics here.

          https://docs.linuxserver.io/images/docker-plex/

          Scroll down a bit to find the docker-compose section. To start a sample plex server, make the following changes:

          Remove network_mode: host

          In line with environment and volumes, add this:
          ports - 324001:32400

          This will route 32400 of the docker container to 32401 of the host network, allowing you to have both servers running at the same time without a port conflict.

          Edit the volumes as needed. Always remember, it goes: host: container for everything. You can change it however you need. /config should preferably be on an SSD, as I said. The rest can be created as needed. For mine, I have both movies and TV shows stored under a folder called /media/. My plex docker script mounts /media/ and in plex I can search through the subdirectories to find the TV and Movies section.

          Your second (temporary) plex server should be set up properly once you start the container

          I’ll tell you how to data over to the Docker container later.

    • exu@feditown.comEnglish
      2·
      4 months ago

      Without docker you still just copy your files from Windows to Linux, though you have to find the right directories for that. Jellyfin can be installed directly on Debian. Just add their repo and go

    • sunstoned@lemmus.orgEnglish
      1·
      4 months ago

      Is there a reason you’re not considering running this in a VM?

      I could see a case where you go for a native install on a virtual machine, attach a virtual disk to isolate your library from the rest of the filesystem, and then move that around (or just straight up mount that directory in the container) as needed.

      That way you can back up your library separately from your JF server implementation and go hog wild.

      • Apathy Tree@lemmy.dbzer0.comOPEnglish
        11·
        4 months ago

        That’s too much work; I don’t know how to do it and have it work; I don’t want to put forth that much effort to learn an entire new dynamic for something literally nobody actually cares about but me… I mean there’s tons of reasons I wouldn’t want to do that.

        As a self-host community that should be like… understood…? But I was apparently wrong to make that assumption. Most of this community can’t even suggest anything that doesn’t involve docker. Which is super lame for low-level hosts.

        • Shabby4582@lemmy.worldEnglish
          1·
          4 months ago

          But this post didn’t suggest Docker, it suggested a VM. This would be a totally sensible thing to do as you can just recreate it if you mess it up. Virtualbox works fine on Windows and Linux. Install it and spin up a distro.

          Mate, the suggestions you have been given for VMs and docker are to help you recover easily should you mess up. If you are going to moan about that…maybe just install bare metal and get on with it yourself?