From f75c17ed295162ed67f2d11c144492cdfaf54a9e Mon Sep 17 00:00:00 2001 From: Zooko O'Whielacronx Date: Tue, 19 Feb 2008 15:34:19 -0700 Subject: [PATCH] docs: change example capability --- docs/using.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/using.html b/docs/using.html index d3443808..e77a78b4 100644 --- a/docs/using.html +++ b/docs/using.html @@ -23,7 +23,7 @@

The CLI

-

Prefer the command-line? Run "tahoe --help" (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 "tahoe ls" work without the --dir-cap= option, you have to put a directory capability (e.g. http://127.0.0.1:8123/uri/URI%3ADIR2%3Ax2pdyrez6nemrby5jzw6lxkxye%3Arl654zxxdppmhgzvaaaxdyf6bhbzbszmmoynm3h7kzuxtlksbynq/) into ~/.tahoe/private/root_dir.cap.

+

Prefer the command-line? Run "tahoe --help" (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 "tahoe ls" work without the --dir-cap= option, you have to put a directory capability (e.g. http://127.0.0.1:8123/uri/URI:DIR2:ovjy4yhylqlfoqg2vcze36dhde:4d4f47qko2xm5g7osgo2yyidi5m4muyo2vjjy53q4vjju2u55mfa) into ~/.tahoe/private/root_dir.cap.

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.S. "CLI" is pronounced "clee".

-- 2.45.2