<h1>The CLI</h1>
- <p>Prefer the command-line? Run "<cite>tahoe --help</cite>" (the same command-line tool that is used to start and stop nodes serves to navigate and use the decentralized filesystem). To make commands like "<cite>tahoe ls</cite>" work without the <cite>--dir-cap=</cite> option, you have to put a directory capability (e.g. <cite>http://127.0.0.1:8123/uri/URI:DIR2:ovjy4yhylqlfoqg2vcze36dhde:4d4f47qko2xm5g7osgo2yyidi5m4muyo2vjjy53q4vjju2u55mfa</cite>) into <cite>~/.tahoe/private/root_dir.cap</cite>.</p>
- <p>As with the WUI (and with all current interfaces to Tahoe), you are responsible for remembering directory capabilities yourself. If you create a new directory and lose the capability to it, then you cannot access that directory ever again.</p>
+ <p>Prefer the command-line? Run "<cite>tahoe --help</cite>" (the same
+ command-line tool that is used to start and stop nodes serves to navigate
+ and use the decentralized filesystem). To get started, create a new
+ directory and mark it as the 'tahoe:' alias by running "<cite>tahoe
+ add-alias tahoe `tahoe mkdir`</cite>". Once you've done that, you can do
+ "<cite>tahoe ls tahoe:</cite>" and "<cite>tahoe cp LOCALFILE
+ tahoe:foo.txt</cite>" to work with your filesystem. The Tahoe CLI uses
+ the same syntax as the well-known scp and rsync tools. See <a
+ href="CLI.txt">CLI.txt</a> for more details.</p>
+
+ <p>As with the WUI (and with all current interfaces to Tahoe), you are
+ responsible for remembering directory capabilities yourself. If you
+ create a new directory and lose the capability to it, then you cannot
+ access that directory ever again.</p>
<p>P.S. "CLI" is pronounced "clee".</p>