A tracker for the LBRY protocol.
Find a file
2013-06-23 22:34:13 -04:00
config package descriptions, unused imports, etc... 2013-06-23 22:34:13 -04:00
example clean-up before bed 2013-06-23 06:21:59 -04:00
server package descriptions, unused imports, etc... 2013-06-23 22:34:13 -04:00
storage package descriptions, unused imports, etc... 2013-06-23 22:34:13 -04:00
.travis.yml initial 2013-06-21 19:31:32 -04:00
AUTHORS initial 2013-06-21 19:31:32 -04:00
CONTRIBUTORS initial 2013-06-21 19:31:32 -04:00
LICENSE initial 2013-06-21 19:31:32 -04:00
main.go scrape+stats foundation; restructuring 2013-06-23 03:56:28 -04:00
README.md fix copypasta induced error 2013-06-23 13:02:12 -03:00

#chihaya Build Status

chihaya is a high-performance BitTorrent tracker written in the Go programming language. It isn't quite ready for prime-time just yet, but these are the features that it targets:

  • Asynchronous and concurrent (multiplexes requests over all available threads)
  • Low processing and memory footprint
  • IPv6 support
  • Storage interface that can be easily adapted to use any data store
  • Scaling properties that directly correlate with the chosen data store's scaling properties

##installing

$ go install github.com/pushrax/chihaya

##configuring

Configuration is done in a JSON formatted file specified with the -config flag. One can start with example/config.json as a base.

##implementing a new storage backend

The storage package works similar to the standard library's database/sql package. To write a new storage backend, create a new Go package that has an implementation of both the Storage and the StorageDriver interfaces. Within your package define an init() function that calls storage.Register(driverName, yourStorageDriver). After that, all you have to do is remember to add import _ path/to/your/library to the top of main.go and now config files will recognize your driver by name.

##contributing

If you're interested in contributing, please contact us in #chihaya on freenode(webchat) or post to the issue tracker. Please don't offer a pull request with no prior communication attempts (unless it's small), as it will most likely lead to confusion and time wasted for everyone. And remember: good gophers always use gofmt!