AutoTorrent allows easy cross-seeding
Project description
Given an input torrent, it will scan your collection for the files in the torrent. If all (or most) the files are found, a folder with links to all the files will be created and the torrent added to rTorrent.
All you need to do is download the torrents and AutoTorrent plays mix and match to make it possible to seed as much as possible across trackers.
Requirements
Linux, BSD, OSX - Something not windows
rTorrent
Python 2.6, 2.7, 3.3, 3.4
Shell / SSH / Putty
Install
From GitHub (develop):
virtualenv autotorrent-env autotorrent-env/bin/pip install git+https://github.com/JohnDoee/autotorrent.git#develop
From PyPi (stable):
virtualenv autotorrent-env autotorrent-env/bin/pip install autotorrent
Configuration
All settings can be found and changed in autotorrent.conf, this file must reside in the same folder as autotorrent is executed from.
general
db - Path to the database file
store_path - Folder where the virtual folders seeded, resides
ignore_files - A comma seperated list of files that should be ignored (supports wildcards)
add_limit_size - Max size, in bytes, the total torrent size is allowed to vary
add_limit_percent - Max percent the total torrent size is allowed to vary
link_type - What kind of link should AutoTorrent make? the options are hard and soft.
the add_limit_* variables allow for downloading of e.g. different NFOs and other small files that makes a difference in the torrents.
client
client - only rtorrent supported right no, so must be rtorrent
url - URL to rtorrent, must be to the XMLRPC server or SCGI server.
label - Label added to torrents when added to rtorrent (used in rutorrent only)
the url supports both SCGI directly and XMLRPC via HTTP. To use scgi, prefix the url with scgi instead of http, e.g. scgi://127.0.0.1:10000/
disks
A list of disks where to build the search database from.
The keys must be sequential, i.e. disk1, disk2, disk3 etc.
Instructions
Start by installing and configuring.
Step 1, build the database with autotorrent -r, this can take some time.
Step 2, have some torrents ready and run autotorrent -a folder/with/torrents/*.torrents, this command will spit out how it went with adding the torrents.
And you’re good to go.
Limitations
Only works with rtorrent
Probably only works on Linux
FAQ
Q: How are files with relative path in the configuration file, found?
The paths should be relative to the configuration file, e.g. /home/user/autotorrent-env/autotorrent.conf, then store_path=store_paths/X/ resolves to /home/user/autotorrent-env/store_path/
Q: I have three sites I cross-seed between, how do you suggest I structure it?
Say, you have site X, Y and Z. You want to seed across the sites as they share lots of content. You download all your data into /home/user/downloads/. For this you will need three configuration file, one for each site.
AutoTorrent is installed into /home/user/autotorrent-env/.
Only store_path is recommended to vary between the configuration files (the others are optional).
store_path for site X - /home/user/autotorrent-env/store_paths/X/
store_path for site Y - /home/user/autotorrent-env/store_paths/Y/
store_path for site Z - /home/user/autotorrent-env/store_paths/Z/
disks paths can be:
disk1=/home/user/downloads/
disk2=/home/user/autotorrent-env/store_paths/X/
disk3=/home/user/autotorrent-env/store_paths/Y/
disk4=/home/user/autotorrent-env/store_paths/Z/
Q: Can I use the same Database file for several configuration files?
Yes, if they have the same disks. Don’t worry about adding the store_path to the disks, AutoTorrent will figure it out.
Q: What problems can occur?
One big problem is that the files are not checked for their actual content, just if their filename matches and size matches. If AutoTorrent tries to use a file that is not complete, then you can end up sending loads of garbage to innocent peers, alhough they should blackball you quite fast.
Q: I want to cross-seed RARed scene releases, what do you think about that?
The actual .rar files must be completely downloaded and the same size. Things that can vary are: nfos, sfvs, samples and subs.
The releases must also have an sfv in the same folder as the rar files files.
Q: What are hardlinks and what are the risks or problems associated with using them?
See: http://www.cyberciti.biz/tips/understanding-unixlinux-symbolic-soft-and-hard-links.html
License
MIT, see LICENSE
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Hashes for autotorrent-1.4.0-py2.py3-none-any.whl
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 | 47e41ec5920826665e07fc202accfd571b11f590d707717d730e50944f910dd3 |
|
| MD5 | 3b3f20d5867b97044e97d34a9eea74bd |
|
| BLAKE2b-256 | 475b8c3e9a0cfc390339b36d9553967c0158d85e0eaf4f1036ac0ae09563f2f6 |
