doc/integration/bittorrent.texi

   1 @node BitTorrent
   2 @cindex BitTorrent integration
   3 @section BitTorrent and huge files
   4
   5 If dealing with @ref{Git}, @ref{Feeds, web feeds} and @ref{Multimedia,
   6 multimedia} goes relatively fast, then BitTorrent and huge files
   7 consumes much time. You can not wait for downloads finish, but want to
   8 queue them after.
   9
  10 @pindex aria2
  11 @url{http://aria2.github.io/, aria2} multi-protocol download utility
  12 could be used for solving that issue conveniently. It supports HTTP,
  13 HTTPS, FTP, SFTP and BitTorrent protocols, together with
  14 @url{http://tools.ietf.org/html/rfc5854, Metalink} format. BitTorrent
  15 support is fully-featured: UDP trackers, DHT, PEX, encryption, magnet
  16 URIs, Web-seeding, selective downloads, LPD. @command{aria2} can
  17 accelerate HTTP*/*FTP downloads by segmented multiple parallel
  18 connections.
  19
  20 @pindex aria2-downloaded.sh
  21 You can queue you files after they are completely downloaded.
  22 @file{aria2-downloaded.sh} contents:
  23
  24 @verbatiminclude aria2-downloaded.sh
  25
  26 Also you can prepare
  27 @url{http://aria2.github.io/manual/en/html/aria2c.html#files, input file}
  28 with the jobs you want to download:
  29
  30 @example
  31 $ cat jobs
  32 http://www.nncpgo.org/download/nncp-0.11.tar.xz
  33     out=nncp.txz
  34 http://www.nncpgo.org/download/nncp-0.11.tar.xz.sig
  35     out=nncp.txz.sig
  36 $ aria2c \
  37     --on-download-complete aria2-downloaded.sh \
  38     --input-file jobs
  39 @end example
  40
  41 and all that downloaded (@file{nncp.txz}, @file{nncp.txz.sig}) files
  42 will be sent to @file{remote.node} when finished.