this post was submitted on 12 Feb 2024
147 points (96.8% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54803 readers
667 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 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
hey Op - I went through the same journey as you recently.
I found the exact same guide you linked - but here's what I found on my journey from knowing literally nothing to having it work.
firstly that guide is a bit outdated and very terse, in fact most of the guides have at least one thing that's outdated and several things not explained
Here were my learning steps:
getting confident with the Linux command line enough that "chmod" and "chown", user:group, rm, nano, and other basic commands weren't foreign to me
getting confident enough with docker and docker compose that I understand what a container, image, compose file are and how to both manipulate them and exec commands inside them
understanding the basics of what a VPN is and does so the terms proxy, reverse proxy, port forwarding, DNS aren't alien to me
understanding the basics of Linux file management including dotfiles, fstab, mounting, blkid, and as mentioned chmod and chown
none of this is particularly hard to grasp once you've grasped it but most guides you see and people you meet along the way will assume all of the above is second nature to you. at first I would pull my hair out seeing suggestions like "have you shelled into the container to curl your public IP?" like what the fuck does that even mean
I started with VPN as thats the important protective part. I paid for Mullvad because its fairly cheap and stuck with it all the way. First I used their GUI app and then later I switched to Tailscale and ran it as an exit node.
I also found guides like YAMS (Yet Another Media Server), dockSTARTer, Trash Guides and the Servarr wiki and would jump between them, Uninstalling, reinstalling, going down paths that didn't work and formatting my raspberry pi and starting from scratch several times. It took me about 6 weeks to skill up to the point where I'm confident knowing about all the parts of my setup.
I'm happy to answer all the questions I can (bear in mind I knew nothing about this a few months ago, but my newbie perspective could help because I know what it's like to not really know what half these terms mean)
PS:to specifically answer "what do these tools do"
Thanks for your answer. I'm well versed in Linux and Docker due to heavy personal and professional use. For me it is a I-cannot-know-what-I-don't-know situation. Your explanations of the tools helps quite a lot. When I have enough time again (maybe at the weekend) I will setup Mullvad and some of the mentioned tools, without loading first. Then, when I'm sure bout the setup I can start