Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

54716 readers

222 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

[email protected]

How to remotely access a Raspberry Pi? (sh.itjust.works)

submitted 1 month ago by [email protected] to c/[email protected]

37 comments fedilink hide all child comments

So I have a Synology server that I have a good deal of experience with, so this post will be through that lens.

What I'd like to do is set up a Raspberry Pi exclusively for pirating. So Qbittorrent and Proton VPN to get started, later Radarr, Lidarr, etc. I don't think I'll have a problem getting the Pi up and running, but I'd like to run it like my server, tucked away somewhere without a monitor or peripherals.

How do I access it? For my Synology box, I just put in a browser the local ip port 5000 and I have a whole desktop right there. But when I google about how I'd access a Pi, everything points to using SSH. I know a lot of people have Pis set up like this and surely they can't be administering the whole thing through CLI, right? How do I get a similar setup to my Synology such that I can just get a desktop interface in a browser?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 11 points 1 month ago (2 children)

Tailscale for remote access
Portainer for GUI docker management
NGINX Proxy Manager running behind tailscale for accessing your services easier (can go into greater detail on this)
SSH for anything else

IMO, trying to avoid CLI in server administration is doing yourself a long term disservice. Its not that challenging and you'll learn a lot more about how everything works. Plus, you're pretty much not going to be able to avoid the terminal forever.

[–] [email protected] 3 points 1 month ago (2 children)

I would love a layman's guide to NGINX. every guide I come across is filled with unexplained jargon

[–] [email protected] 3 points 3 weeks ago (1 children)

https://lemmy.browntown.dev/post/1440768

Not sure if you getting mentioned in the post gives you a notification, but just wanted to drop the link here! Hope it helps, I tried to make the walkthrough pretty basic while still keeping it high level where it matters (like I assume anyone attempting this is familiar enough with selfhosting that they can install a docker container without me walking through the entire process)

[–] [email protected] 3 points 3 weeks ago

appreciate it thanks, I'll take a look

yes, I can run docker.

[–] [email protected] 5 points 4 weeks ago

Sounds good! I'll write something up & post on selfhosted

Just give me a couple days :)

[–] [email protected] 4 points 1 month ago (1 children)

Yeah, I'm not trying to avoid terminal completely, just for the day to day tasks I'm gonna use it for. But someone in another thread pointed out that most things, after they're set up have a front end GUI, like your portainer example. I can get comfortable with such a situation.

[–] [email protected] 3 points 4 weeks ago

Like others have said, running a DE with remote capabilities will be a lot of overhead.

If you set up portainer and watchtower using ssh, you can pretty much just manage everything from portainer while watchtower makes sure that portainer and the rest of your containers stay updated. It's a very hands-off operation, especially if you set up auto updates on top of that for the pi OS. You'll probably just have to ssh in periodically to run a system upgrade and maybe restart to update the kernel.