Hints

Tahoe-LAFS runs in userspace!

You do not have to run tahoe as root! Tahoe-LAFS runs fine as any user with privileges to write to the disk, access the network, etc.

If there are caveats to this, please let me know and document them here!

Make Tahoe automatically start on reboots

I just put tahoe start in my crontab for the user under which tahoe is running with the following:

@reboot /path/to/tahoe start

You may need to add the -C command line option if you are running tahoe from a non-standard directory.

Dependencies

The following packages are required.

pyopenssl or python-openssl depending on your distribution.

Cheats

Create a Reverse Proxy for controlled web access to a web gateway

We have written a page documenting "Reverse Proxy."

Suggestions

It is suggested that a deep check and lease refresh be run on a regular basis. A deep check is recommended to be run monthly for each alias containing data you wish to keep and is initiated with the following command:

tahoe deep-check --repair ALIAS

...where ALIAS is the alias of the directory for which you wish to retain data. If you use the default alias of "tahoe", no ALIAS need be specified.

Leases are refreshed with the following command:

tahoe deep-check --add-lease ALIAS

A detailed explanation of the tahoe garbage collection process may be found here: https://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/docs/garbage-collection.rst

Hint: Both the deep check and lease refresh may be combined into a single command:

tahoe deep-check --repair --add-lease ALIAS

-- SteveDodson - 2012-02-29

Hacks

Topic revision: r6 - 2012-02-29 - SteveDodson