WUI is more useful than CLI #1415
Labels
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
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#1415
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
There are things that the WUI can do (e.g., attenuate caps, list a directory and show all the various caps of entries) that can't be done in the CLI. Using the WUI usually involves using web browsers which handle secrets as URLs and form contents, rather than solely as passwords. While some people prefer WUI-type interfaces, given the security issues it's bad to encourage their use by having the CLI be less capable.
This ticket is really about things the WUI can do that involve capabilities. I don't have an objection to the status page not being implemented in the CLI.
Attenuating caps using the CLI is #1299.
To include URIs in directory listings, use the
--uri
and--readonly-uri
options totahoe ls
. These are documented intahoe ls --help
; is there anything else we could do to make them more discoverable?I found ls --json, which addresses my need (really understand directory contents and see all the data that is there). I don't have a good answer for why I didn't read the help.
Perhaps "get" on a directory should suggest ls --json. Between that and ls --json, that more or less obviates the need for get to work on directories.
Also see #1856 (CLI command to generate an incident report).