A tracker for the LBRY protocol.
Find a file
2017-06-03 14:14:37 +02:00
bittorrent *: add structured logging 2017-05-07 04:30:22 -04:00
cmd/chihaya cmd/chihaya: move cpuprofile into postrun 2017-05-07 18:52:17 -04:00
dist dist/helm: move from contrib/helm 2017-06-03 14:14:37 +02:00
docs docs: remove deniability middleware 2017-02-16 01:04:17 -05:00
frontend frontend: make request timing optional 2017-05-12 20:27:31 +02:00
middleware *: add structured logging 2017-05-07 04:30:22 -04:00
pkg pkg/prometheus: init 2017-05-01 15:56:16 -04:00
storage memory: add metrics for peers 2017-05-29 19:04:40 +02:00
.travis.yml http: use go1.8 graceful shutdown 2017-02-18 13:08:12 +01:00
CONTRIBUTING.md readme: add CONTRIBUTING.md 2016-03-30 01:21:53 -04:00
Dockerfile dockerfile: delete the compiler from the container 2016-10-21 23:01:22 -04:00
example_config.yaml memory: add metrics for peers 2017-05-29 19:04:40 +02:00
glide.lock http: use go1.8 graceful shutdown 2017-02-18 13:08:12 +01:00
glide.yaml http: use go1.8 graceful shutdown 2017-02-18 13:08:12 +01:00
LICENSE Bring in more old behaviour, use types for peer_id and infohash 2016-03-02 21:05:31 -05:00
MAINTAINERS add leo to maintainers 2016-08-16 22:17:10 -04:00
README.md README: update development section 2017-01-31 19:34:45 -05:00

Chihaya

Build Status Docker Repository on Quay.io Go Report Card GoDoc License IRC Channel

Note: The master branch may be in an unstable or even broken state during development. Please use releases instead of the master branch in order to get stable binaries.

Chihaya is an open source BitTorrent tracker written in Go.

Differentiating features include:

  • Protocol-agnostic middleware
  • HTTP and UDP frontends
  • IPv4 and IPv6 support
  • YAML configuration
  • Metrics via Prometheus

Why Chihaya?

Chihaya is built for developers looking to integrate BitTorrent into a preexisting production environment. Chihaya's pluggable architecture and middleware framework offers a simple and flexible integration point that abstracts the BitTorrent tracker protocols. The most common use case for Chihaya is integration with the deployment of cloud software.

Production Use

Facebook

Facebook uses BitTorrent to deploy new versions of their software. In order to optimize the flow of traffic within their datacenters, Chihaya is configured to prefer peers within the same subnet. Because Facebook organizes their network such that server racks are allocated IP addresses in the same subnet, the vast majority of deployment traffic never impacts the congested areas of their network.

CoreOS

Quay is a container registry that offers the ability to download containers via BitTorrent in order to speed up large or geographically distant deployments. Announce URLs from Quay's torrent files contain a JWT in order to allow Chihaya to verify that an infohash was approved by the registry. By verifying the infohash, Quay can be sure that only their content is being shared by their tracker.

Development

Getting Started

Building from HEAD

In order to compile the project, the latest stable version of Go and knowledge of a working Go environment are required.

$ mkdir chihaya
$ export GOPATH=$PWD/chihaya
$ go get -t -u github.com/chihaya/chihaya/...
$ $GOPATH/bin/chihaya --help

Reproducible Builds

Reproducible builds are handled by using glide to vendor dependencies.

$ cd $GOPATH/src/github.com/chihaya/chihaya
$ glide install
$ go install github.com/chihaya/chihaya/...
$ $GOPATH/bin/chihaya --help

Docker

Docker containers are available for HEAD and stable releases.

Testing

The following will run all tests and benchmarks. Removing -bench will just run unit tests.

$ go test -bench $(glide novendor | grep -v contrib)

Contributing

Long-term discussion and bug reports are maintained via GitHub Issues. Code review is done via GitHub Pull Requests. Real-time discussion is done via freenode IRC.

For more information read CONTRIBUTING.md.

Architecture

 +----------------------+
 |  BitTorrent Client   |<--------------+
 +----------------------+               |
             |                          |
             |                          |
             |                          |
+------------v--------------------------+-------------------+-------------------------+
|+----------------------+   +----------------------+frontend|                  chihaya|
||        Parser        |   |        Writer        |        |                         |
|+----------------------+   +----------------------+        |                         |
|            |                          ^                   |                         |
+------------+--------------------------+-------------------+                         |
+------------v--------------------------+-------------------+                         |
|+----------------------+   +----------------------+   logic|                         |
||  PreHook Middleware  |-->|  Response Generator  |<-------|-------------+           |
|+----------------------+   +----------------------+        |             |           |
|                                                           |             |           |
|+----------------------+                                   | +----------------------+|
|| PostHook Middleware  |-----------------------------------|>|       Storage        ||
|+----------------------+                                   | +----------------------+|
|                                                           |                         |
+-----------------------------------------------------------+-------------------------+

BitTorrent clients send Announce and Scrape requests to a Frontend. Frontends parse requests and write responses for the particular protocol they implement. The TrackerLogic interface to is used to generate responses for their requests and optionally perform a task after responding to a client. A configurable chain of PreHook and PostHook middleware is used to construct an instance of TrackerLogic. PreHooks are middleware that are executed before the response has been written. After all PreHooks have executed, any missing response fields that are required are filled by reading out of the configured implementation of the Storage interface. PostHooks are asynchronous tasks that occur after a response has been delivered to the client. Request data is written to the storage asynchronously in one of these PostHooks.

  • BitTorrent.org: a static website containing the BitTorrent spec and all BEPs
  • OpenTracker: a popular BitTorrent tracker written in C
  • Ocelot: a private BitTorrent tracker written in C++