this post was submitted on 06 Apr 2024
25 points (93.1% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54758 readers
271 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
Ko-fi | Liberapay |
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
As @slickJujitsu@lemmy.today said, make sure to set everything up using Docker containers going forward, it makes stuff like this completely painless.
As for your *aars, pretty sure all you have to do is create and export/download a backup in the web GUI, all your stuff including file history, settings, and stuff should follow. Check the documentation for each tool to verify before you do anything destructive though, it’s been a little while since I had to change hardware without everything being Dockerized.
For Plex, read them follow this guide step by step. It’s not generally that painful of a process. I’m assuming your pirated media is not saved locally on the Windows machine, and is on a NAS, in the cloud, or on external drives? If so there’s nothing destructive about copying files and standing up a new instance, so just follow the guide and don’t delete anything from the Windows PMS instance until you’re done setting up the new Dockerized PMS on Linux. That also goes for the *aar services.
Once everything’s Dockerized every time you update you’re effectively migrating servers, the Docker image is meant to be ephemeral. All the config folders, temp folders, media folders, log folders, etc., are mapped to permanent folders on the host that can just be attached to whatever new host you want to use.
One thing I will add is don’t map specific media library folders to your PMS Docker image, like
/movies
,/tv
,/music
, etc. Instead, make an inclusive/media
folder, nest the Library folders in there, then pass that inclusive/media
folder to the PMS Docker image. This way you don’t have to edit your compose yaml file each time you want to add a new Library, you just create the new folder, add the content, and map the Library in the PMS GUI.Awesome write up, thanks for taking the time!
Definitely seems like docker is the way to go. I've currently got my NAS connected via ISCSI, but will I need to change that up when moving to docker?
No. As long as you can mount the share on your Linux machine, you then just pass that share to the Docker container the same way you’d pass a mounted SMB share or a locally mounted directory.
Sweet, I didn't think so, but doesn't hurt to check!