2014-12-17 03:22:46 +00:00
|
|
|
Similar to the [[web]] special remote, git-annex can use BitTorrent as
|
|
|
|
|
a source for files that are added to the git-annex repository.
|
|
|
|
|
|
|
|
|
|
It supports both `.torrent` files, and `magnet:` links. When you run `git
|
|
|
|
|
annex addurl` with either of these, it will download the contents of the
|
|
|
|
|
torrent and add it to the git annex repository.
|
|
|
|
|
|
|
|
|
|
See [[tips/using_the_web_as_a_special_remote]] for usage examples.
|
|
|
|
|
|
|
|
|
|
git-annex uses [aria2](http://aria2.sourceforge.net/) to download torrents.
|
2014-12-18 18:22:43 +00:00
|
|
|
|
|
|
|
|
If git-annex is not built using the haskell torrent library to parse
|
2015-05-30 14:54:14 +00:00
|
|
|
torrents, it also needs the `btshowmetainfo` program, from either
|
|
|
|
|
bittornado or the original BitTorrent client.
|
2014-12-17 03:22:46 +00:00
|
|
|
|
2023-01-09 19:49:20 +00:00
|
|
|
The bittorrent special remote is always enabled, without any manual setup being
|
|
|
|
|
needed. Its name is "bittorrent".
|
|
|
|
|
|
2014-12-17 03:22:46 +00:00
|
|
|
## notes
|
|
|
|
|
|
|
|
|
|
Currently git-annex only supports downloading content from a torrent;
|
|
|
|
|
it cannot upload or remove content.
|
|
|
|
|
|
|
|
|
|
Multi-file torrents are supported; to handle them, `git annex addurl`
|
2014-12-17 18:43:36 +00:00
|
|
|
will add a directory containing all the files from the torrent.
|
2014-12-18 19:58:28 +00:00
|
|
|
|
|
|
|
|
It's hard to say if a torrent is healthy enough to let a file be downloaded
|
|
|
|
|
from it, and harder to predict if a torrent will stay healthy. So,
|
|
|
|
|
git-annex takes a cautious approach and when dropping a file, won't
|
|
|
|
|
treat this special remote as one of the required [[copies]]. It's probably
|
|
|
|
|
a good idea to configure git-annex to fully distrust this remote, by
|
|
|
|
|
running `git annex untrust bittorrent`
|
