bittorrent-tracker/README.md

148 lines
4.6 KiB
Markdown
Raw Normal View History

2014-06-07 22:41:06 +00:00
# bittorrent-tracker [![build](https://img.shields.io/travis/feross/bittorrent-tracker.svg)](https://travis-ci.org/feross/bittorrent-tracker) [![npm](https://img.shields.io/npm/v/bittorrent-tracker.svg)](https://npmjs.org/package/bittorrent-tracker) [![npm downloads](https://img.shields.io/npm/dm/bittorrent-tracker.svg)](https://npmjs.org/package/bittorrent-tracker) [![gittip](https://img.shields.io/gittip/feross.svg)](https://www.gittip.com/feross/)
2014-03-26 08:37:13 +00:00
2014-03-27 07:39:14 +00:00
#### Simple, robust, BitTorrent tracker (client & server) implementation
2014-03-26 08:37:13 +00:00
2014-03-27 07:45:25 +00:00
![tracker](https://raw.githubusercontent.com/feross/bittorrent-tracker/master/img.png)
2014-03-26 08:37:13 +00:00
Node.js implementation of a [BitTorrent tracker](https://wiki.theory.org/BitTorrentSpecification#Tracker_HTTP.2FHTTPS_Protocol), client and server.
A **BitTorrent tracker** is an HTTP service which responds to GET requests from BitTorrent
clients. The requests include metrics from clients that help the tracker keep overall
statistics about the torrent. The response includes a peer list that helps the client
participate in the torrent.
Also see [bittorrent-dht](https://github.com/feross/bittorrent-dht). This module is used
2014-03-26 08:37:13 +00:00
by [WebTorrent](http://webtorrent.io).
2014-03-28 04:08:20 +00:00
## features
- Includes client & server implementations
2014-04-19 08:38:36 +00:00
- Supports HTTP & UDP trackers ([BEP 15](http://www.bittorrent.org/beps/bep_0015.html))
2014-05-12 00:29:12 +00:00
- Supports tracker scrape
2014-03-28 04:08:20 +00:00
2014-03-27 07:45:25 +00:00
## install
2014-03-26 08:37:13 +00:00
```
npm install bittorrent-tracker
```
2014-03-27 07:45:25 +00:00
## usage
2014-03-27 07:39:14 +00:00
2014-03-27 07:45:25 +00:00
### client
2014-03-26 08:37:13 +00:00
To connect to a tracker, just do this:
```js
var Client = require('bittorrent-tracker')
2014-03-26 08:37:13 +00:00
var parseTorrent = require('parse-torrent')
2014-06-06 08:21:01 +00:00
var fs = require('fs')
2014-03-26 08:37:13 +00:00
var torrent = fs.readFileSync(__dirname + '/torrents/bitlove-intro.torrent')
var parsedTorrent = parseTorrent(torrent) // { infoHash: 'xxx', length: xx, announce: ['xx', 'xx'] }
var peerId = new Buffer('01234567890123456789')
var port = 6881
var client = new Client(peerId, port, parsedTorrent)
client.on('error', function (err) {
// fatal client error!
2014-03-26 08:37:13 +00:00
console.log(err.message)
})
client.on('warning', function (err) {
2014-03-26 08:37:13 +00:00
// a tracker was unavailable or sent bad data to the client. you can probably ignore it
console.log(err.message)
2014-03-26 08:37:13 +00:00
})
2014-03-26 09:11:27 +00:00
// start getting peers from the tracker
client.start()
2014-03-26 08:37:13 +00:00
client.on('update', function (data) {
2014-05-12 00:29:12 +00:00
console.log('got an announce response from tracker: ' + data.announce)
console.log('number of seeders in the swarm: ' + data.complete)
console.log('number of leechers in the swarm: ' + data.incomplete)
2014-03-26 08:37:13 +00:00
})
client.once('peer', function (addr) {
console.log('found a peer: ' + addr) // 85.10.239.191:48623
})
2014-03-26 09:11:27 +00:00
// announce that download has completed (and you are now a seeder)
client.complete()
2014-03-26 08:37:13 +00:00
2014-03-26 09:11:27 +00:00
// force a tracker announce. will trigger more 'update' events and maybe more 'peer' events
client.update()
2014-03-26 08:37:13 +00:00
2014-03-26 09:11:27 +00:00
// stop getting peers from the tracker, gracefully leave the swarm
client.stop()
2014-05-12 00:29:12 +00:00
// scrape
2014-06-06 08:21:01 +00:00
client.scrape()
2014-05-12 00:29:12 +00:00
client.on('scrape', function (data) {
console.log('got a scrape response from tracker: ' + data.announce)
console.log('number of seeders in the swarm: ' + data.complete)
console.log('number of leechers in the swarm: ' + data.incomplete)
console.log('number of total downloads of this torrent: ' + data.incomplete)
})
2014-03-26 08:37:13 +00:00
```
2014-03-27 07:45:25 +00:00
### server
2014-03-27 07:39:14 +00:00
To start a BitTorrent tracker server to track swarms of peers:
2014-03-26 08:37:13 +00:00
```js
var Server = require('bittorrent-tracker').Server
2014-05-24 01:06:29 +00:00
var server = new Server({
udp: true, // enable udp server? [default=true]
http: true // enable http server? [default=true]
})
2014-03-27 07:36:46 +00:00
server.on('error', function (err) {
2014-05-24 01:05:18 +00:00
// fatal server error!
console.log(err.message)
})
server.on('warning', function (err) {
// client sent bad data. probably not a problem, just a buggy client.
2014-03-27 07:36:46 +00:00
console.log(err.message)
})
2014-07-04 03:05:02 +00:00
server.on('listening', function (port) {
console.log('tracker server is now listening on ' + port)
2014-03-27 07:36:46 +00:00
})
2014-03-27 07:47:12 +00:00
// start tracker server listening!
server.listen(port)
2014-03-27 07:36:46 +00:00
// listen for individual tracker messages from peers:
server.on('start', function (addr) {
2014-03-27 07:36:46 +00:00
console.log('got start message from ' + addr)
})
server.on('complete', function (addr) {})
server.on('update', function (addr) {})
server.on('stop', function (addr) {})
2014-03-27 07:36:46 +00:00
// get info hashes for all torrents in the tracker server
Object.keys(server.torrents)
// get the number of seeders for a particular torrent
server.torrents[infoHash].complete
// get the number of leechers for a particular torrent
server.torrents[infoHash].incomplete
// get the peers who are in a particular torrent swarm
server.torrents[infoHash].peers
2014-03-26 08:37:13 +00:00
```
2014-07-04 03:05:02 +00:00
The http server will handle requests for the following paths: `/announce`, `/scrape`. Requests for other paths will not be handled.
2014-03-26 08:37:13 +00:00
## license
MIT. Copyright (c) [Feross Aboukhadijeh](http://feross.org).