Saber, a complete solution for PT users. Build Status
Homepage: https://github.com/SaberSalv/saber
Author: Saber
License: MIT-LICENSE
Documentation: https://github.com/SaberSalv/saber/wiki
Issue Tracker: https://github.com/SaberSalv/saber/issues
Operation Systems: Linux, Mac OS X

Features:

  • Add Torrent: send a torrent file from website to rutorrent.
  • Upload: upload a torrent file from command line to the site.
  • Fetch: automatically/manually fetch files from seedbox to home-laptop.
  • Other Tasks:
    • Make: make a torrent file and copy it to local and remote watch directory.
    • Send: send files from home-laptop to seedbox.
    • Clean: remove files which are not seeded in rtorrent.

you can find more tools at here.

Getting Started

Create ~/.saberrc configuration file from template.

Add Torrent

See saber-addtorrent project.

Upload

Because of lacking APIs in major PT sites, so I write this small script to help uploading a torrent from cmdline. Good news is BTN v2.0 will include API. And BTN already has an official autobot which grabs scene releases. :)

Support sites: BIB, bB, STP

Support upload types: ebook, magazine

Manual fill <info-data>.yml file and upload it.

$ saber g magazine hello.pdf
> create hello.yml
$ edit hello.yml

    type: magazines
    title: Hello
    description: Hello World
    ...

$ saber.bib upload pdf hello.yml
> it opens a firefox browser
> it fills data and submit it
> upload complete

Auto fill <info-data>.yml file from ISBN.

$ saber g ebook hello.epub:1781100055
> create hello.yml

Fetch

AutoFetch

Start saber-server at server side.

$ saber server -V

Start saber-client at client side.

$ aria2c --enable-rpc --save-session session.lock -i session.lock
$ saber client -V

Test if it works

(server) $ saber drb_add <rtorrent_file_hash_id> saber -V
(client) > aria2 should begin download file from ftp://seedbox/bt/<file>

Automatically fetch: when a file is finished download in rutorrent with label 'saber', then it'll add to aria2.

Manually fetch: right click 'Saber Fetch' in rutorrent web ui, then it'll add to aria2.

Or from command line, send a download file to client: saber drb_add <hash_id> saber, sometime the client need a long time(2 minutes) to recive the file list sent by server.

ManualFetch

Begin fetch a file from seedbox

$ saber fetch foo
> begin to download ftp://seedbox/bt/foo/a.epub via aria2
> begin to download ftp://seedbox/bt/foo/b.epub via aria2

Tasks

Make

Make a torrent

$ saber.bib make hello.epub
> mktorrent -p -a ANNOUNCE_URL hello.epub
> cp hello.epub.torrent ~/bt/watch 
> rsync -Phr hello.epub.torrent user@host:bt/watch

Send

Send files to seedbox

$ saber send1 hello.epub bt
> rsync -ahP hello.epub user@host:bt

Clean

Clean up unseeded files in rtorrent.

$ saber clean

Use saber help to list all tasks. use saber help upload to find specific task help.

Install

Main article: Install Saber

$ gem install saber

Development Dependency Status Code Climate

Contributing

  • Submit any bugs/features/ideas to github issue tracker.

Please see Contibution Documentation.

A list of Contributors.

(the MIT License)

Copyright (c) 2011-2012 Saber

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.