Welcome to the Tahoe-LAFS project, a secure, decentralized, fault-tolerant filesystem. About Tahoe-LAFS.
This procedure has been verified to work on Windows, Cygwin, Mac, many flavors of Linux, Solaris, FreeBSD, OpenBSD, and NetBSD. It's likely to work on other platforms. If you have trouble getting Tahoe-LAFS running this way, please write to the tahoe-dev mailing list, where friendly hackers will help you out.
Check if you already have an adequate version of Python installed by running python -V. Python v2.4 (v2.4.4 or greater), Python v2.5 or Python v2.6 will work. Python v3 does not work. On Windows, we recommend the use of Python v2.6. If you don't have one of these versions of Python installed, then follow the instructions on the Python download page to download and install Python v2.6. Make sure that the path to the installation directory has no spaces in it (e.g. on Windows, do not install Python in the "Program Files" directory).
If you are on Windows, you now must manually install the pywin32 package from the pywin32 site before getting Tahoe-LAFS. Make sure to get the correct file for the version of Python you are using — e.g. ending in "py2.6.exe" for Python 2.6. If using 64-bit Windows, the file should have "win-amd64" in its name.
Download the 1.7.0 zip file:
http://tahoe-lafs.org/source/tahoe-lafs/releases/allmydata-tahoe-1.7.0.zip
Unpack the zip file and cd into the top-level directory.
Run python setup.py build to generate the tahoe executable in a subdirectory of the current directory named bin.
Optionally run python setup.py test to verify that it passes all of its self-tests.
Run bin/tahoe --version to verify that the executable tool prints out the right version number.
Now you are ready to deploy a decentralized filesystem. The tahoe executable in the bin directory can configure and launch your Tahoe-LAFS nodes. See running.html for instructions on how to do that.
For optional features such as tighter integration with your operating system's package manager, you can see the AdvancedInstall wiki page. The options on that page are not necessary to use Tahoe-LAFS and can be complicated, so we do not recommend following that page unless you have unusual requirements for advanced optional features. For most people, you should first follow the instructions on this page, and if that doesn't work then ask for help by writing to the tahoe-dev mailing list.