forked from tahoe-lafs/tahoe-lafs
/
install.html
69 lines (44 loc) · 3.26 KB
/
install.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
<!DOCtype HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html lang="en">
<head>
<title>Installing Tahoe</title>
<link rev="made" class="mailto" href="mailto:zooko[at]zooko[dot]com">
<meta name="description" content="how to install Tahoe">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="keywords" content="tahoe secure decentralized filesystem installation">
</head>
<body>
<h1>About Tahoe</h1>
<p>Welcome to <a href="http://allmydata.org">the Tahoe project</a>, a secure, decentralized, fault-tolerant filesystem.</p>
<p>See <a href="about.html">the about page</a> for more information.
<h1>
<h1>How To Install Tahoe</h1>
<p>This procedure has been verified to work on Windows, Cygwin, Mac, Linux, Solaris, and FreeBSD. It's likely to work on other platforms. If you have trouble with this install process, please write to <a href="http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev">the tahoe-dev mailing list</a>, where friendly hackers will help you out.</p>
<h2>Satisfy the Dependencies</h2>
<p>Prior to installing Tahoe ensure that the following are installed:
<ol>
<li><a href="http://gcc.gnu.org/">g++</a> >= v3.3 -- the "Cygwin" version of gcc/g++ works for Cygwin and for Windows; the "Mac Developer Tools" version of gcc/g++ works for Mac</li>
<li><a href="http://gnu.org/software/make/">GNU make</a></li>
<li><a href="http://python.org">Python</a> >= v2.4.2 including development headers i.e. "Python.h"</li>
</ol>
<h2>Get the Source Code</h2>
<p>Download a recent release tarball file from:</p>
<pre><a
href="http://allmydata.org/source/tahoe/releases">http://allmydata.org/source/tahoe/releases</a></pre>
<p>The larger <tt>-SUMO</tt> tarballs include all the
automatically-installable dependencies; use the smaller regular tarball
if you don't mind the build process downloading the things it needs, or
if you've downloaded and unpacked the <tt><a
href="http://allmydata.org/source/tahoe/deps/tahoe-deps.tar.gz">http://allmydata.org/source/tahoe/deps/tahoe-deps.tar.gz</a></tt>
bundle.</p>
<h2>Build Tahoe</h2>
<p>Unpack the tarball and cd into the top-level directory.</p>
<p>Run <cite>make</cite> to build and to install the <cite>tahoe</cite> executable into a subdirectory of the current directory named <cite>bin</cite>.</p>
<p>Run <cite>make test</cite> to verify that it built correctly and passes all tests.</p>
<p>Run <cite>bin/tahoe --version</cite> to verify that the executable tool runs and prints out the right version number (the "allmydata" version number is the version number of the Tahoe package).</p>
<h2>Run</h2>
<p>Now you have the Tahoe source code installed and are ready to use it to form a decentralized filesystem. The <cite>tahoe</cite> executable in the <cite>bin</cite> directory can configure and launch your Tahoe node. See <a href="running.html">running.html</a> for instructions on how to do that.</p>
<h2>More Details</h2>
<p>For more details, including platform-specific hints for debian, windows, and Mac systems, please see the <a href="http://allmydata.org/trac/tahoe/wiki/InstallDetails">InstallDetails</a> wiki page.</p>
</body>
</html>