Ticket #1704: quickstart-out-of-line-urls.diff.patch

File quickstart-out-of-line-urls.diff.patch, 5.7 KB (added by zooko, at 2012-03-31T16:22:45Z)

  • docs/quickstart.rst 

    diff --git a/docs/quickstart.rst b/docs/quickstart.rst
index 4e8844b..ce579c3 100644
    a b  
     1
    12==================
    23Getting Tahoe-LAFS
    34==================
    45
    5 Welcome to `the Tahoe-LAFS project <https://tahoe-lafs.org>`_, a secure,
    6 decentralized, fault-tolerant storage system. `About Tahoe-LAFS
    7 <about.rst>`_.
     6Welcome to `the Tahoe-LAFS project`_, a secure, decentralized, fault-tolerant
     7storage system. `About Tahoe-LAFS`_.
     8
     9.. _the Tahoe-LAFS project: https://tahoe-lafs.org
     10.. _About Tahoe-LAFS: file:about.rst
    811
    912How To Get Tahoe-LAFS
    1013=====================
    1114
    12 This procedure has been verified to work on Windows, Mac, OpenSolaris,
    13 and too many flavors of Linux and of BSD to list. It's likely to work
    14 on other platforms.
     15This procedure has been verified to work on Windows, Mac, OpenSolaris, and
     16too many flavors of Linux and of BSD to list. It's likely to work on other
     17platforms.
    1518
    1619In Case Of Trouble
    1720------------------
    1821
    19 There are a few 3rd party libraries that Tahoe-LAFS depends on that
    20 might not be easy to set up on your platform. If the following
    21 instructions don't Just Work without any further effort on your part,
    22 then please write to `the tahoe-dev mailing list
    23 <https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev>`_ where
    24 friendly hackers will help you out.
     22There are a few 3rd party libraries that Tahoe-LAFS depends on that might not
     23be easy to set up on your platform. If the following instructions don't Just
     24Work without any further effort on your part, then please write to `the tahoe-dev mailing list`_ where friendly hackers will help you out.
     25
     26.. _the tahoe-dev mailing list: https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
    2527
    2628Install Python
    2729--------------
    2830
    29 Check if you already have an adequate version of Python installed by
    30 running ``python -V``. Python v2.4 (v2.4.4 or greater), Python v2.5,
    31 Python v2.6, or Python v2.7 will work. Python v3 does not work. On
    32 Windows, we recommend the use of Python v2.6 (native, not Cygwin). If
    33 you don't have one of these versions of Python installed, then follow
    34 the instructions on `the Python download page
    35 <http://www.python.org/download/releases/2.6.6/>`_ to download and
    36 install Python v2.6. Make sure that the path to the installation
    37 directory has no spaces in it (e.g. on Windows, do not install Python
    38 in the "Program Files" directory).
     31Check if you already have an adequate version of Python installed by running
     32``python -V``. Python v2.4 (v2.4.4 or greater), Python v2.5, Python v2.6, or
     33Python v2.7 will work. Python v3 does not work. On Windows, we recommend the
     34use of native Python, not Cygwin. If you don't have one of these versions of
     35Python installed, download and install `Python v2.7`_. Make sure that the
     36path to the installation directory has no spaces in it (e.g. on Windows, do
     37not install Python in the "Program Files" directory).
     38
     39.. _Python v2.7: http://www.python.org/download/releases/2.7.2/
    3940
    4041Get Tahoe-LAFS
    4142--------------
    4243
    43 `Download the latest stable release, v1.9.1
    44 <https://tahoe-lafs.org/source/tahoe-lafs/releases/allmydata-tahoe-1.9.1.zip>`_
     44Download the latest stable release, `Tahoe-LAFS v1.9.1`_.
     45
     46.. _Tahoe-LAFS v1.9.1: https://tahoe-lafs.org/source/tahoe-lafs/releases/allmydata-tahoe-1.9.1.zip
    4547
    4648Set Up Tahoe-LAFS
    4749-----------------
    … … Set Up Tahoe-LAFS 
    4951Unpack the zip file and cd into the top-level directory.
    5052
    5153Run ``python setup.py build`` to generate the ``tahoe`` executable in a
    52 subdirectory of the current directory named ``bin``. This will download
    53 and build anything you need from various websites.
     54subdirectory of the current directory named ``bin``. This will download and
     55build anything you need from various websites.
    5456
    55 On Windows, the ``build`` step might tell you to open a new Command
    56 Prompt (or, on XP and earlier, to log out and back in again). This is
    57 needed the first time you set up Tahoe-LAFS on a particular
    58 installation of Windows.
     57On Windows, the ``build`` step might tell you to open a new Command Prompt
     58(or, on XP and earlier, to log out and back in again). This is needed the
     59first time you set up Tahoe-LAFS on a particular installation of Windows.
    5960
    60 Optionally run ``python setup.py test`` to verify that it passes all of
    61 its self-tests.
     61Optionally run ``python setup.py test`` to verify that it passes all of its
     62self-tests.
    6263
    63 Run ``bin/tahoe --version`` (on Windows, ``bin\tahoe --version``) to
    64 verify that the executable tool prints out the right version number.
     64Run ``bin/tahoe --version`` (on Windows, ``bin\tahoe --version``) to verify
     65that the executable tool prints out the right version number.
    6566
    6667Run Tahoe-LAFS
    6768--------------
    6869
    6970Now you are ready to deploy a decentralized filesystem. The ``tahoe``
    70 executable in the ``bin`` directory can configure and launch your
    71 Tahoe-LAFS nodes. See `running.rst <running.rst>`_ for instructions on
    72 how to do that.
    73 
    74 Advanced Installation
    75 ---------------------
    76 
    77 For optional features such as tighter integration with your operating
    78 system's package manager, you can see the `AdvancedInstall
    79 <https://tahoe-lafs.org/trac/tahoe-lafs/wiki/AdvancedInstall>`_ wiki page.
    80 The options on that page are not necessary to use Tahoe-LAFS and can be
    81 complicated, so we do not recommend following that page unless you have
    82 unusual requirements for advanced optional features. For most people,
    83 you should first follow the instructions on this page, and if that
    84 doesn't work then ask for help by writing to `the tahoe-dev mailing
    85 list <https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev>`_.
     71executable in the ``bin`` directory can configure and launch your Tahoe-LAFS
     72nodes. See running.rst_ for instructions on how to do that.
    8673
     74.. _running.rst: file:running.rst