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

54476 readers

496 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

db0@lemmy.dbzer0.com

sunbrothersco@lemmy.dbzer0.com

dataprolet@lemmy.dbzer0.com

Flatworm7591@lemmy.dbzer0.com

RandomLegend@lemmy.dbzer0.com

switching to an *arr stack - questions (lemmy.dbzer0.com)

submitted 1 year ago by BigNerdAlert@lemmy.dbzer0.com to c/piracy@lemmy.dbzer0.com

7 comments fedilink hide all child comments

TLDR can the *arr stack be setup to move the completed files to another server?

Before I potentially waste many hours trying to get this setup, need a bit of advice.

Been old school for a couple of decades. Running a Linux box on bare metal with a torrent client. Client gets downloads from a RSS feed and when completed, I manually copy them to my Linux server (Big JBOD), and use filebot to rename and move them to the various directories.

Been interested in switching to something more automated for a while and want to give sonarr etc. a go.

I already have a proxmox box running a few VMs so was thinking of setting up docker on there with the various sonarr, radarr, etc. and then have the completed files moved over to my linux server. The server was built around 2010 and great for streaming but I think running docker and everything else would kill it.

It is possible to set it up so that when the download is finished on the docker box, it's copied across to the server?

All the guides I've read suggest having the docker stack on the same box as the server but I'm reluctant because if it's age.

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

[–] whyNotSquirrel@sh.itjust.works 1 points 1 year ago

I think the main reason to keep the data on the same datastorage is to continue seeding your torrents without duplicating the files.

*arr services are renaming the downloaded file into a library with metadata that are used by your player or service (Kodi/Jellyfin/Plex) therefore if you want that your torrents client continue seeding after the download you need to keep the file like it was: The solution is hardlink and it only works on the same datastorage, because you just copy the links to a file not the data itself (basically)

if your server and datastorage are on the same local network you could simply mount a remote folder on the server hosting the torrent client so it download directly on the other system that has the storage?

That's what I'm doing currently as "temporary" solution (almost a year now...)

Services (sonarr, radarr, Jackett, Jellyfin, transmission/...) on a Raspberry Pi 4

Raid 5 storage on my computer for the TV Shows Raid 1 storage on a NAS for the movies

Both shared via NFS and mounted on the raspberry pi

(yeah it means i have to keep my computer, my Nas and the raspberry pi ON all the time)