2014-09-25 16:47:19 +00:00
|
|
|
.. -*- coding: utf-8-with-signature-unix; fill-column: 77 -*-
|
2013-11-08 20:31:08 +00:00
|
|
|
|
2011-05-10 19:16:50 +00:00
|
|
|
==================
|
|
|
|
Getting Tahoe-LAFS
|
|
|
|
==================
|
|
|
|
|
2012-04-01 01:57:17 +00:00
|
|
|
Welcome to `the Tahoe-LAFS project`_, a secure, decentralized, fault-tolerant
|
|
|
|
storage system.
|
|
|
|
|
|
|
|
`about Tahoe-LAFS <about.rst>`__
|
|
|
|
|
|
|
|
.. _the Tahoe-LAFS project: https://tahoe-lafs.org
|
2011-05-10 19:16:50 +00:00
|
|
|
|
|
|
|
How To Get Tahoe-LAFS
|
|
|
|
=====================
|
|
|
|
|
2012-04-01 01:57:17 +00:00
|
|
|
This procedure has been verified to work on Windows, Mac, OpenSolaris, and
|
|
|
|
too many flavors of Linux and of BSD to list. It's likely to work on other
|
|
|
|
platforms.
|
2011-05-10 19:16:50 +00:00
|
|
|
|
|
|
|
In Case Of Trouble
|
|
|
|
------------------
|
|
|
|
|
2012-04-01 01:57:17 +00:00
|
|
|
There are a few 3rd party libraries that Tahoe-LAFS depends on that might not
|
|
|
|
be easy to set up on your platform. If the following instructions don't Just
|
|
|
|
Work without any further effort on your part, then please write to `the
|
|
|
|
tahoe-dev mailing list`_ where friendly hackers will help you out.
|
|
|
|
|
|
|
|
.. _the tahoe-dev mailing list: https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
|
2011-05-10 19:16:50 +00:00
|
|
|
|
|
|
|
Install Python
|
|
|
|
--------------
|
|
|
|
|
2012-04-01 01:57:17 +00:00
|
|
|
Check if you already have an adequate version of Python installed by running
|
2014-09-25 16:47:19 +00:00
|
|
|
``python -V``. Python v2.6 (v2.6.6 or greater recommended) or Python v2.7
|
|
|
|
will work. Python v3 does not work. On Windows, we recommend the use of
|
|
|
|
native Python v2.7, not Cygwin Python. If you don't have one of these
|
|
|
|
versions of Python installed, download and install `Python v2.7`_. 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).
|
2012-04-01 01:57:17 +00:00
|
|
|
|
2013-04-18 03:34:01 +00:00
|
|
|
.. _Python v2.7: http://www.python.org/download/releases/2.7.4/
|
2011-05-10 19:16:50 +00:00
|
|
|
|
|
|
|
Get Tahoe-LAFS
|
|
|
|
--------------
|
|
|
|
|
2013-04-25 00:17:45 +00:00
|
|
|
Download the latest stable release, `Tahoe-LAFS v1.10.0`_.
|
2012-04-01 01:57:17 +00:00
|
|
|
|
2013-04-25 00:17:45 +00:00
|
|
|
.. _Tahoe-LAFS v1.10.0: https://tahoe-lafs.org/source/tahoe-lafs/releases/allmydata-tahoe-1.10.0.zip
|
2011-05-10 19:16:50 +00:00
|
|
|
|
|
|
|
Set Up Tahoe-LAFS
|
|
|
|
-----------------
|
|
|
|
|
|
|
|
Unpack the zip file and cd into the top-level directory.
|
|
|
|
|
2013-10-05 17:55:01 +00:00
|
|
|
Run "``python setup.py build``" to generate the ``tahoe`` executable in a
|
2012-04-01 01:57:17 +00:00
|
|
|
subdirectory of the current directory named ``bin``. This will download and
|
|
|
|
build anything you need from various websites.
|
2011-05-10 19:16:50 +00:00
|
|
|
|
2012-04-01 01:57:17 +00:00
|
|
|
On Windows, the ``build`` step might tell you to open a new Command Prompt
|
|
|
|
(or, on XP and earlier, to log out and back in again). This is needed the
|
|
|
|
first time you set up Tahoe-LAFS on a particular installation of Windows.
|
2011-05-10 19:16:50 +00:00
|
|
|
|
2014-09-25 16:47:19 +00:00
|
|
|
Run "``bin/tahoe --version``" (on Windows, "``bin\tahoe --version``") to
|
|
|
|
verify that the executable tool prints out the right version number after
|
2012-06-01 21:01:04 +00:00
|
|
|
"``allmydata-tahoe:``".
|
2011-05-10 19:16:50 +00:00
|
|
|
|
2014-09-25 16:47:19 +00:00
|
|
|
Optionally run "``python setup.py trial``" to verify that it passes all of
|
|
|
|
its self-tests.
|
2012-09-14 02:10:12 +00:00
|
|
|
|
2011-05-10 19:16:50 +00:00
|
|
|
Run Tahoe-LAFS
|
|
|
|
--------------
|
|
|
|
|
2011-10-30 17:44:11 +00:00
|
|
|
Now you are ready to deploy a decentralized filesystem. The ``tahoe``
|
2012-04-01 01:57:17 +00:00
|
|
|
executable in the ``bin`` directory can configure and launch your Tahoe-LAFS
|
|
|
|
nodes. See `<running.rst>`__ for instructions on how to do that.
|