Version 72 (modified by zooko, at 2009-03-24T01:46:27Z) (diff)

better link to RelatedProjects


Views into the process of Tahoe hackery.

Developer Docs

  • the docs/ directory <-- most core doc is in the source tree here
  • Capabilities: help to clear up confusion about readcaps and writecaps and verifycaps, etc



  • Tahoe has a programmatic API which enables building custom applications on top of the storage infrastructure.
  • The docs/frontends/webapi.txt document shows how to control a Tahoe node programmatically.
  • The Extension Page lists extension projects and extension development resources.

Source Code

  • To fetch the source code using darcs v2: darcs get --lazy tahoe
    • darcs v2 is highly recommended over darcs v1. If you really don't want to install darcs v2, then you can use darcs v1 instead, but you'll have to run a slightly different command-line and be prepared to wait for tens of minutes for the initial get to finish. The command-line for darcs v1 is: darcs get tahoe.
  • contains snapshots of current source code.
  • The Buildbot page (linked at the top of each page) shows current build and test results. See the BuildbotPolicy page.
  • The Timeline (linked at the top of each page) shows changes to the source code, the issue tickets, and the wiki (i.e. this web site).
  • The code coverage statistics show which lines of code get exercised by the unit tests.
  • The Packaging page shows our currently policy for how to re-use 3rd-party libraries and how to distribute Tahoe to users.
  • How to Submit Patches
  • CodingStandards


See Also

Related Projects

  • Foolscap -- Python remote objects done right.
  • zfec -- erasure coding library and command-line tool.
  • pycryptopp -- Python wrappers for the Crypto++ library.