85
Continue Seeding (sh.itjust.works)
submitted 1 year ago by to c/piracy@lemmy.dbzer0.com
33 comments fedilink hide all child comments
 

How do you guys continue seeding? I end up having to move files off my yarr pc drive and onto other drives or my nas because they get too big. I want to continue seeding anything I get though for a while.

you are viewing a single comment's thread
view the rest of the comments
[–] 20 points 1 year ago* (5 children)

A NAS, an SBC eg a raspberry pi, and NFS shares are the basic setup. Everything else essentially builds on this.

  • permalink
  • fedilink
  • source
  • hideshow 5 child comments
    •
  • [–] 2 points 1 year ago* (4 children)

    Everything else essentially builds on this.

    Not really though...I'm running everything related to torrenting and streaming in docker on the same bare metal with a 32tb array of HDDs in it, everything is just stored in the torrent downloads folder and organized with hardlinks in the jellyfin directory.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 3 points 1 year ago (3 children)

    ...which is exactly my point. Using a VM or docker to run the relevant programs and using hard links rather than NFS shares is just a more complicated (but more efficient) setup that follows the same logic. It also has a more complicated network setup for VPN use than running a VPN client on an SBC. That's why an SBC is the easiest way in to the lifestyle, before graduating to the more complicated yet more powerful setups.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 4 points 1 year ago* (1 child)

    I really can't see how it follows the same logic...you're talking about distributed computing using multiple computers, I'm talking about a single piece of hardware which handles it internally.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 1 year ago

    Historically NFS and using one service per server was the usual process. "Builds on" means that the newer processes were developments and improvements to older processes. For example NFS was released in the 1980s and Docker in 2013. Obviously the efficiencies in docker and hyperconverged servers are the reason they have taken over most set ups, but it's not obvious that software such as docker would have come into existence without the original networking processes.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 3 points 1 year ago

    Using a VM or docker to run the relevant programs and using hard links rather than NFS shares is just a more complicated setup

    What? Multiple hosts + network shares is easier than hosting everything in one place?

  • permalink
  • fedilink
  • source
  • parent