== Tahoe-LAFS Tips & Tricks ==

=== git-annex can use Tahoe-LAFS as a backend ===

[http://git-annex.branchable.com/special_remotes/ git-annex special remotes]

=== Back caps/URIs up ===

Tahoe-LAFS users can encrypt their caps (new text file or ~/.tahoe/private/aliases) and upload it to [http://docs.google.com Google Docs], which now accepts arbitrary file types.

=== Publish iCal calendars over Tahoe-LAFS ===

[http://allmydata.org/pipermail/tahoe-dev/2009-July/002219.html Instructions]

=== Automatic Tahoe-LAFS file repair ===

[http://allmydata.org/pipermail/tahoe-dev/2009-October/003012.html Instructions]

=== Host [http://bazaar-vcs.org Bazaar] repositories ===

Support for Tahoe-LAFS's FTP server has been merged into Bzr's mainline ([https://bugs.launchpad.net/tahoe-lafs/+bug/294709 #294709]). It may be preferable to use SFTP, though.

=== Perforce backend storage ===

[http://allmydata.org/pipermail/tahoe-dev/2009-June/002105.html Instructions]

=== Running with supervisord ===

The only trick with [http://supervisord.org supervisord] is to make tahoe run as a single foreground process so it can be watched and killed correctly. Use a command like "bin/tahoe run -C /path/to/tahoe/home".

=== Using Pagekite to run storage nodes behind a NAT ===

[http://tahoe-lafs.org/pipermail/tahoe-dev/2011-July/006534.html Instructions]

[https://pagekite.net/wiki/OpenSource/ Pagekite] is an alternative to reverse-tunneling, especially if you don't have your own proxy and can't forward ports through your NAT. It's also a good way to set up multiple hostnames, any one of which can be used to access your node if the others go down.

=== Mount tahoe-lafs with pyfilesystem and Dokan on Windows XP ===

[wiki:pyFilesystem]