tahoe-lafs/trac-2024-07-25
2
0
Issues1.1k Wiki

command-line: access to uris #105

New Issue
Closed
opened 2007-08-15 19:36:45 +00:00 by zooko · 8 comments
zooko commented 2007-08-15 19:36:45 +00:00

It might be cool if you could peek and poke at URIs as well as at vdrive paths with the cmdline clients.

It might be cool if you could peek and poke at URIs as well as at vdrive paths with the cmdline clients.
zooko added the
code-frontend
minor
enhancement
0.4.0
 labels 2007-08-15 19:36:45 +00:00
zooko added this to the undecided milestone 2007-08-15 19:36:45 +00:00
zooko self-assigned this 2007-08-15 19:36:45 +00:00
zooko modified the milestone from undecided to 0.6.0 2007-08-15 21:33:37 +00:00
zooko commented 2007-08-20 18:00:44 +00:00
Author

This is part of the "improved command-line" task. I would like to see it done for v0.6.

This is part of the "improved command-line" task. I would like to see it done for v0.6.
zooko changed title from command-line access to uris to command-line: access to uris 2007-08-23 19:54:45 +00:00
zooko modified the milestone from 0.6.0 to 0.7.0 2007-09-19 23:01:03 +00:00
warner commented 2007-10-31 07:46:51 +00:00

maybe 'tahoe ls --uri', which could list the URI for each child in addition to its name

and maybe 'tahoe set PATH/NEWCHILD URI' ?

maybe 'tahoe ls --uri', which could list the URI for each child in addition to its name and maybe 'tahoe set PATH/NEWCHILD URI' ?
zooko commented 2007-10-31 15:21:41 +00:00
Author

That sounds good.

That sounds good.
zooko added
0.6.1
 and removed
0.4.0
 labels 2007-10-31 15:21:41 +00:00
zooko commented 2007-11-01 18:09:35 +00:00
Author

We're focussing on an imminent v0.7.0 (see the roadmap) which hopefully has [ -- Small Distributed Mutable Files] and also a fix for [ -- bad SHA-256]. So I'm bumping less urgent tickets to v0.7.1.

We're focussing on an imminent v0.7.0 (see [the roadmap](http://allmydata.org/trac/tahoe/roadmap)) which hopefully has [#197 #197 -- Small Distributed Mutable Files] and also a fix for [#199 #199 -- bad SHA-256]. So I'm bumping less urgent tickets to v0.7.1.
zooko commented 2007-11-13 18:28:57 +00:00
Author

We need to choose a manageable subset of desired improvements for v0.7.1, scheduled for two week hence, so I'm bumping this one into v0.7.2, scheduled for mid-December.

We need to choose a manageable subset of desired improvements for [v0.7.1](http://allmydata.org/trac/tahoe/milestone/0.7.1), scheduled for two week hence, so I'm bumping this one into [v0.7.2](http://allmydata.org/trac/tahoe/milestone/0.7.2), scheduled for mid-December.
zooko added
0.7.0
 and removed
0.6.1
 labels 2007-11-13 18:28:57 +00:00
zooko added
code-frontend-cli
 and removed
code-frontend
 labels 2008-01-15 21:37:20 +00:00
zooko added this to the undecided milestone 2008-01-23 04:21:22 +00:00
warner commented 2008-06-01 21:49:59 +00:00

I agree. I don't know what the syntax should be yet.

Incidentally, now "tahoe ls --uri" will display the URIs of the listed objects, and --readonly-uri will show only read-caps.

I agree. I don't know what the syntax should be yet. Incidentally, now "tahoe ls --uri" will display the URIs of the listed objects, and --readonly-uri will show only read-caps.
warner commented 2008-09-26 02:49:10 +00:00

I think this is done, we can do 'tahoe get URI' and 'tahoe put WRITE-CAP' (for mutable files). Please give the current CLI code a spin and see if it meets your goals.

I think this is done, we can do 'tahoe get URI' and 'tahoe put WRITE-CAP' (for mutable files). Please give the current CLI code a spin and see if it meets your goals.
davidsarah commented 2010-06-13 01:41:51 +00:00
Owner

It appears that this was fixed two years ago, in r2586.

It appears that this was fixed two years ago, in r2586.
tahoe-lafs added the
fixed
 label 2010-06-13 01:41:51 +00:00
tahoe-lafs modified the milestone from eventually to 1.1.0 2010-06-13 01:41:51 +00:00
davidsarah closed this issue 2010-06-13 01:41:51 +00:00
Sign in to join this conversation.
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
1.1.0
No Assignees
zooko
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#105
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?