premiere
/
premiere-deluge-docker
4
3
Fork 1
Code Issues 1 Pull Requests 1 Releases Wiki Activity
Docker container for premiere deulge
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2 Commits
1 Branch
0 Tags
27 KiB
 
 
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'master'
${ noResults }
Go to file
fake bb9a2fb791
dont use .dev tag on deluge, more docs 		3 years ago
Dockerfile dont use .dev tag on deluge, more docs 3 years ago
README.md dont use .dev tag on deluge, more docs 3 years ago
build.sh dont use .dev tag on deluge, more docs 3 years ago

README.md

Premiere Deluge Docker

This helps build the premiere Deluge plugin and libtorrent inside of a Docker container. To read more about what premiere mode does, see below.

How to install

  1. Install Docker (instructions here https://docs.docker.com/engine/install/)
  2. Run docker build . -t premiere-deluge in the same directory as this repo's Dockerfile
  3. Run docker run --network host -it premiere-deluge
  4. You should be able to connect to the web UI running locally on port 8112
  5. Default password is "deluge"
  6. Right click torrents and select "Premiere Mode" to put them in premiere mode

What is "Premiere Mode"?

Setting a torrent to premiere mode causes all of its pieces to become unavailble to peers except the first piece. After all peers in the swarm have completely downloaded the first piece, the second piece gets announced as available and peers may download it. This continues on until the last piece.

This plugin requires a forked version of libtorrent that supports setting pieces into premiere mode.

How do I make my downloads and config persistent?

You need to mount directories on your host machine into your Docker container. Try adding -v /path/to/your/downloads:/root/Downloads and -v /path/to/your/.config:/root/.config to your docker run command to mount these.

Can I run this without Docker?

Yes, the build.sh script sets up everything inside the Docker container and should work outside of one as well (some paths may need to be changed of course).