TAHOE(1)
π TAHOE(1) β the secure distributed file store, bestie edition π
okay so like. the manual name is tahoe, it lives in section 1 (User Commands), and I am going to tell you everything about it. grab a snack. π
β¨ NAME β¨
tahoe β a secure distributed file store. that's it, that's the whole vibe. π¦
β¨ SYNOPSIS β¨
tahoe [global-options] <command> [command-options]
β¨ DESCRIPTION β¨
Tahoe-LAFS is a Free and Open decentralized cloud storage system. no cap. it spreads your data across multiple servers, and here's the iconic part: even if some of those servers fail or get straight-up taken over by an attacker, the entire file store keeps functioning correctly, preserving your privacy and security. main character energy fr fr. π
the tahoe executable is your girl for creating and managing client/server nodes, manipulating the file store, and doing a bunch of debugging/maintenance tasks. she does it all. π
please go peek at the SEE ALSO section at the bottom of this page for pointers to further instructions β it's giving helpful. π«Ά
β¨ GLOBAL OPTIONS β¨
these work everywhere, they're the universal constants of the tahoe universe:
-d,--node-directory=β specify which Tahoe node directory should be used. this directory should either contain a full Tahoe node, or a file namednode.urlthat points to some other Tahoe node. it should also contain a file namedprivate/aliaseswhich contains the mapping from alias name to root dirnode URI. [default for most commands:$HOME/.tahoe]--eliot-destination=β add an Eliot logging destination. may be given more than once. (yes, stack them, queen.)--helpβ display help and exit. classic.--help-eliot-destinationsβ emit usage information for--eliot-destination.-q,--quietβ operate silently. π€«-V,--versionβ display version numbers.--wormhole-invite-appid=β the appid to use on the wormhole server. [default:tahoe-lafs.org/invite]--wormhole-server=β the magic wormhole server to use. [default:ws://wormhole.tahoe-lafs.org:4000/v1] π
β¨ COMMANDS β¨
the tahoe runner can be used for various tasks depending on the command used:
tahoe COMMAND [OPTION]... [NODEDIR]
β¨ ADMINISTRATION β¨
create node configurations and securely invite clients to a grid. it's giving HR department but for a decentralized storage network. πβ¨
COMMANDS
create-nodeβ create a node that acts as a client, server or both. multitasking icon.create-clientβ create a client node (providing storage to others is initially disabled).create-introducerβ create an introducer node. when the grid is large or very dynamic, introducers make it easier for clients to connect. see "Static Server Definitions" in the documentation on how to configure clients to connect to one or more storage servers without using an introducer.inviteβ invite a new node to a grid. see "Magic Wormhole Invites" in the documentation. ππ³οΈ
OPTIONS
-C,--basedir=β same as the global--node-directoryoption.-n,--nickname=β specify the nickname for this node (create-nodeandcreate-clientonly).-i,--introducer=β specify the introducer FURL to use (create-nodeandcreate-clientonly).--hostname=β hostname to automatically set--location/--portwhen--listen=tcp(the default).-p,--webport=β specify which TCP port to run the HTTP interface on. usenoneto disable. Default:tcp:3456:interface=127.0.0.1(create-nodeandcreate-clientonly).--no-storageβ do not offer storage service to other nodes (create-nodeonly). keeping your storage to yourself, valid. π
β¨ CONTROLLING NODES β¨
so in the past, the tahoe command offered service watching (with start, restart, stop commands), but this was not very portable and has been deprecated. rip to a real one. π
COMMANDS
runβ run a node without daemonizing. this is the only command for running nodes. the way that there is literally no other option... periodt.
OPTIONS
--allow-stdin-closeβ do not exit when stdin closes (tahoe runotherwise will exit). this is required for some service runners (likesystemd, for example).-C,--basedir=β same as the global--node-directoryoption.--helpβ display help and exit. this includes lots oftwistd-optionsfor debugging, logging, profiling, et cetera that are left out of this manual page for brevity. (ngl, there's a lot hiding in there.)
β¨ USING THE FILE STORE β¨
all the following commands require pointing tahoe to a running client node with the --node-directory (-d) option (or, alternatively, using the default location).
please run tahoe COMMAND --help for more details on each command. iykyk. π
COMMANDS
mkdirβ create a directory and return its capability ("dircap").add-aliasβ add an alias for an existing cap.create-aliasβ create an alias pointing to a new cap.list-aliasesβ list all alias caps.lsβ list a directory.getβ retrieve a file from the grid.putβ upload a file into the grid.cpβ copy one or more files or directories.unlinkβ unlink a file or directory on the grid.rmβ same asunlink.mvβ move a file within the grid.lnβ make an additional link to an existing file or directory.backupβ make target dir look like local dir. β¨webopenβ open a web browser to a grid file or directory.manifestβ list all files/directories in a subtree.statsβ print statistics about all files/directories in a subtree.checkβ check a single file or directory.deep-checkβ check all files/directories reachable from a starting point. going deep. π₯
β¨ DEBUGGING β¨
the following commands are useful for developers and for troubleshooting. nerd mode activated. π€π
tahoe debug SUBCOMMAND [OPTION]... [PARAMETER]...
please run e.g. tahoe debug dump-share --help for more details on each subcommand.
SUBCOMMANDS
dump-shareβ unpack and display the contents of a share.dump-capβ unpack a read-cap or write-cap.find-sharesβ locate sharefiles in node directories.catalog-sharesβ describe all shares in node dirs.corrupt-shareβ corrupt a share by flipping a bit. π (yes, on purpose, it's a debugging tool, breathe.)flogtoolβ utilities to access log files.
β¨ AUTHORS β¨
Tahoe-LAFS has been written by Brian Warner, Zooko Wilcox-O'Hearn and dozens of others. this manpage was originally written by bertagaz. legends, all of them. ππ
β¨ REPORTING BUGS β¨
please see https://tahoe-lafs.org/trac/tahoe-lafs/wiki/HowToReportABug.
Tahoe-LAFS home page: https://tahoe-lafs.org/
tahoe-dev mailing list: https://lists.tahoe-lafs.org/mailman/listinfo/tahoe-dev
found a bug? tell them!! they wanna know!! besties fix things together π«Ά
β¨ COPYRIGHT β¨
Copyright Β© 2006β2025 The Tahoe-LAFS Software Foundation.
β¨ SEE ALSO β¨
run tahoe --help for an overview of commands and tahoe <command> --help for more details on each command.
see https://tahoe-lafs.readthedocs.io/en/tahoe-lafs-1.20.0/frontends/CLI.html for user documentation specific to the tahoe command.
see https://tahoe-lafs.readthedocs.io/ for "the documentation" β in-depth, longer-form explanations, specifications and step-by-step tutorials. π
and that's the whole thing!! this page is from the Tahoe-LAFS β tahoe command era, dated May 2025, and it's the TAHOE(1) manual β go build something decentralized and gorgeous, bestie. πβ¨ππ¦πΈ
π¦ where this page comes from
- debian trixie: tahoe-lafs 1.20.0-6 Β· GPL-2.0-or-later OR TGPPL-1.0+
- nixos 26.05: tahoe-lafs 1.20.0-unstable-2025-10-12
- ubuntu questing: tahoe-lafs 1.20.0-6
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms