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

53948 readers

454 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

💰 Please help cover server costs.

founded 1 year ago

MODERATORS

[email protected]

1487

Torrent client rankings (lemmy.basedcount.com)

submitted 11 months ago by [email protected] to c/[email protected]

250 comments fedilink hide all child comments

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

[–] [email protected] 20 points 11 months ago (1 children)

Seconded for Transmission. It's light on features because (as far as I know) it's the only ine in this list that's built to run unattended in a Docker container, with a web interface.

[–] [email protected] 10 points 11 months ago (1 children)

Qbitorrent, rtorrent and deluge can be run via docker with a web interface.

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

Yes but running a web interface on top of rtorrent is not as easy as transmision.

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

If you're trying to build it all from scratch, sure, but you specifically mentioned docker and there's plenty of high-quality docker images you can use - and it's no harder to use a qBittorrent docker image than a transmission docker image.

Here's the docker command for transmission:

docker run -d \
  --name=transmission \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Etc/UTC \
  -e TRANSMISSION_WEB_HOME= `#optional` \
  -e USER= `#optional` \
  -e PASS= `#optional` \
  -e WHITELIST= `#optional` \
  -e PEERPORT= `#optional` \
  -e HOST_WHITELIST= `#optional` \
  -p 9091:9091 \
  -p 51413:51413 \
  -p 51413:51413/udp \
  -v /path/to/data:/config \
  -v /path/to/downloads:/downloads \
  -v /path/to/watch/folder:/watch \
  --restart unless-stopped \
  lscr.io/linuxserver/transmission:latest

and the equivelant for qBitTorrent:

docker run -d \
  --name=qbittorrent \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Etc/UTC \
  -e WEBUI_PORT=8080 \
  -p 8080:8080 \
  -p 6881:6881 \
  -p 6881:6881/udp \
  -v /path/to/appdata/config:/config \
  -v /path/to/downloads:/downloads \
  --restart unless-stopped \
  lscr.io/linuxserver/qbittorrent:latest

I'm not even going to argue that the qBitTorrent docker image is technically easier as it has less to configure, it's all one command at the end of the day.

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

I don't want to argue about that, I personally avoid Docker if I can, but can't deny it's a great tool and very powerful for the right use cases.

What I wonder is: to you, in your opinion, those commands are really easier than "apt install transmission"?

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

If you read up through the thread, the person I responded to specifically said about transmission being the easiest to run via docker.

[–] [email protected] 1 points 11 months ago

Oh, my apologies.

[–] [email protected] 3 points 11 months ago

Qbittorrent-nox is available as a package on all major distors afaik. It has an official docker image aswell. Couldn't be any simpler to set up.