| 1 | 1 patch for repository zooko@dev.allmydata.org:/home/darcs/tahoe-lafs/trunk: |
|---|
| 2 | |
|---|
| 3 | Fri Jan 28 08:07:00 MST 2011 zooko@zooko.com |
|---|
| 4 | * docs: edit running.html, change "http://allmydata.org" to "http://tahoe-lafs.org" in NEWS and README.txt, add Josh Wilcox to CREDITS for his contribution of doc patches |
|---|
| 5 | |
|---|
| 6 | New patches: |
|---|
| 7 | |
|---|
| 8 | [docs: edit running.html, change "http://allmydata.org" to "http://tahoe-lafs.org" in NEWS and README.txt, add Josh Wilcox to CREDITS for his contribution of doc patches |
|---|
| 9 | zooko@zooko.com**20110128150700 |
|---|
| 10 | Ignore-this: 133a97d7c9e9401f2754d83f64733d1d |
|---|
| 11 | ] { |
|---|
| 12 | hunk ./CREDITS 130 |
|---|
| 13 | E: ravi@p-static.net |
|---|
| 14 | D: converted docs from .txt to .rst |
|---|
| 15 | |
|---|
| 16 | +N: Josh Wilcox |
|---|
| 17 | +D: docs |
|---|
| 18 | + |
|---|
| 19 | replace ./Makefile [A-Za-z_0-9\-\.] allmydata.org tahoe-lafs.org |
|---|
| 20 | hunk ./NEWS 68 |
|---|
| 21 | |
|---|
| 22 | - We now host binary packages so that users on certain operating systems |
|---|
| 23 | can install without having a compiler. |
|---|
| 24 | - <http://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-lafs-dep-eggs/README.html> |
|---|
| 25 | + <http://allmydata.org/source/tahoe-lafs/deps/tahoe-lafs-dep-eggs/README.html> |
|---|
| 26 | - Use a newer version of a dependency if needed, even if an older |
|---|
| 27 | version is installed. This would previously cause a VersionConflict |
|---|
| 28 | error. (#1190) |
|---|
| 29 | replace ./NEWS [A-Za-z_0-9\-\.] allmydata.org tahoe-lafs.org |
|---|
| 30 | hunk ./README.txt 26 |
|---|
| 31 | See `TGPPL.PDF`_ for why the TGPPL exists, graphically illustrated on three slides. |
|---|
| 32 | |
|---|
| 33 | .. _quickstart.html: http://allmydata.org/source/tahoe-lafs/trunk/docs/quickstart.html |
|---|
| 34 | -.. _COPYING.GPL: http://tahoe-lafs.org/trac/dupfilefind/browser/COPYING.GPL |
|---|
| 35 | -.. _COPYING.TGPPL.html: http://tahoe-lafs.org/source/dupfilefind/trunk/COPYING.TGPPL.html |
|---|
| 36 | -.. _TGPPL.PDF: http://tahoe-lafs.org/~zooko/tgppl.pdf |
|---|
| 37 | +.. _COPYING.GPL: http://allmydata.org/trac/dupfilefind/browser/COPYING.GPL |
|---|
| 38 | +.. _COPYING.TGPPL.html: http://allmydata.org/source/dupfilefind/trunk/COPYING.TGPPL.html |
|---|
| 39 | +.. _TGPPL.PDF: http://allmydata.org/~zooko/tgppl.pdf |
|---|
| 40 | replace ./README.txt [A-Za-z_0-9\-\.] allmydata.org tahoe-lafs.org |
|---|
| 41 | hunk ./docs/running.html 14 |
|---|
| 42 | <body> |
|---|
| 43 | <h1>How To Run Tahoe-LAFS</h1> |
|---|
| 44 | |
|---|
| 45 | - <p>This is how to run a Tahoe-LAFS client or a complete Tahoe-LAFS grid. First you |
|---|
| 46 | - have to install the Tahoe-LAFS software, as documented in <a |
|---|
| 47 | - href="install.html">install.html</a>.</p> |
|---|
| 48 | + <p>This is how to run a Tahoe-LAFS client to connect to an |
|---|
| 49 | + existing grid, or how to set up a complete Tahoe-LAFS grid. First |
|---|
| 50 | + you have to install the Tahoe-LAFS software, as documented |
|---|
| 51 | + in <a href="install.html">install.html</a>.</p> |
|---|
| 52 | |
|---|
| 53 | <p>The <code>tahoe</code> program in the <code>bin</code> directory is |
|---|
| 54 | used to create, start, and stop nodes. Each node lives in a separate base |
|---|
| 55 | hunk ./docs/running.html 24 |
|---|
| 56 | directory, in which there is a configuration file named <code>tahoe.cfg</code>. Nodes |
|---|
| 57 | read and write files within this base directory.</p> |
|---|
| 58 | |
|---|
| 59 | - <p>A grid consists of a set of <em>storage nodes</em> and <em>client nodes</em> |
|---|
| 60 | - running the Tahoe-LAFS code. There is also an <em>introducer node</em> that |
|---|
| 61 | - is responsible for getting the other nodes talking to each other.</p> |
|---|
| 62 | + <p>A grid consists of a set of <em>storage nodes</em> |
|---|
| 63 | + and <em>client nodes</em> (also known as <em>gateway nodes</em>) |
|---|
| 64 | + running the Tahoe-LAFS code. There is also an <em>introducer |
|---|
| 65 | + node</em> that is responsible for getting the other nodes talking |
|---|
| 66 | + to each other. Which grid of storage servers your client will |
|---|
| 67 | + connect to is determined solely by the introducer—if you configure |
|---|
| 68 | + your node to connect to a certain introducer then your node will |
|---|
| 69 | + only use those storage servers provided by that introducer. If you |
|---|
| 70 | + configure your node to connect to a new introducer of your own |
|---|
| 71 | + creation (see below), then your node will not connect to any |
|---|
| 72 | + storage servers until you've created some storage servers and told them |
|---|
| 73 | + to register themselves with that introducer.</p> |
|---|
| 74 | |
|---|
| 75 | <p>If you're getting started we recommend you try connecting to |
|---|
| 76 | the <a href="http://tahoe-lafs.org/trac/tahoe-lafs/wiki/TestGrid">the |
|---|
| 77 | hunk ./docs/running.html 39 |
|---|
| 78 | - public test grid</a> as you only need to create a client node. |
|---|
| 79 | - When you want to create your own grid you'll need to create the |
|---|
| 80 | - introducer and several initial storage nodes (see the note about |
|---|
| 81 | - small grids below).</p> |
|---|
| 82 | + public test grid</a>—you will need to create only a gateway node |
|---|
| 83 | + to do that. When you want to create your own grid you'll need to |
|---|
| 84 | + create the introducer and several initial storage nodes (see the |
|---|
| 85 | + note about small grids below).</p> |
|---|
| 86 | |
|---|
| 87 | <p>If the Tahoe-LAFS <code>bin</code> directory is not on your PATH, then |
|---|
| 88 | in all the command lines below, specify the full path to <code>bin/tahoe</code>.</p> |
|---|
| 89 | hunk ./docs/running.html 129 |
|---|
| 90 | <h3>The SFTP and FTP frontends</h3> |
|---|
| 91 | |
|---|
| 92 | <p>You can access your Tahoe-LAFS grid via any <a href="http://en.wikipedia.org/wiki/SSH_file_transfer_protocol">SFTP</a> or |
|---|
| 93 | - <a href="http://en.wikipedia.org/wiki/File_Transfer_Protocol">FTP</a> client. |
|---|
| 94 | + <a href="http://en.wikipedia.org/wiki/File_Transfer_Protocol">FTP</a> client. |
|---|
| 95 | See <a href="frontends/FTP-and-SFTP.rst">FTP-and-SFTP.rst</a> for how to set this up. |
|---|
| 96 | On most Unix platforms, you can also use SFTP to plug Tahoe-LAFS into your computer's |
|---|
| 97 | local filesystem via <code>sshfs</code>. |
|---|
| 98 | hunk ./docs/running.html 133 |
|---|
| 99 | - |
|---|
| 100 | + |
|---|
| 101 | <p>The <a href="http://tahoe-lafs.org/trac/tahoe-lafs/wiki/SftpFrontend">SftpFrontend</a> page |
|---|
| 102 | on the wiki has more information about using SFTP with Tahoe-LAFS.</p> |
|---|
| 103 | |
|---|
| 104 | hunk ./setup.py 6 |
|---|
| 105 | |
|---|
| 106 | # Tahoe-LAFS -- secure, distributed storage grid |
|---|
| 107 | # |
|---|
| 108 | -# Copyright © 2008-2010 Allmydata, Inc. |
|---|
| 109 | +# Copyright © 2008-2011 Allmydata, Inc. |
|---|
| 110 | # |
|---|
| 111 | # This file is part of Tahoe-LAFS. |
|---|
| 112 | # |
|---|
| 113 | } |
|---|
| 114 | |
|---|
| 115 | Context: |
|---|
| 116 | |
|---|
| 117 | [setup: adjust tests to use the new interface of check_requirement which has a 3-tuples instead of a 2-tuple |
|---|
| 118 | zooko@zooko.com**20110128141546 |
|---|
| 119 | Ignore-this: d4c6197c78c156e7ae3c3444d81db9ed |
|---|
| 120 | fixes #1339 |
|---|
| 121 | ] |
|---|
| 122 | [src/allmydata/__init__.py: fix #1339, give an indication in the --version[-and-path] output of when the imported setuptools is distribute, and use a separate element in _vers_and_locs_list tuples for information other than the package name and location. This also changes slightly how the sqlite version is reported. |
|---|
| 123 | david-sarah@jacaranda.org**20110128054150 |
|---|
| 124 | Ignore-this: 47e8d2afed1f8114681e9094dc93276 |
|---|
| 125 | ] |
|---|
| 126 | [TAG allmydata-tahoe-1.8.2b1 |
|---|
| 127 | warner@lothar.com**20110126061431] |
|---|
| 128 | Patch bundle hash: |
|---|
| 129 | 76ceb24dbc21423b2d4f23de7a3124fbd10240c7 |
|---|
