v0.7.0 documentation #241
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#241
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 is a lot of documentation that needs to be updated to fit v0.7.0 of tahoe. This ticket is for me to keep notes about which documents need to change in what way.
webapi.txt uses the word "node" to mean either a tahoe wapi/wui server, a tahoe storage server, or a file-or-directory in the filesystem. Disambiguate these, probably by using "webapi server", "storage server", and "file or directory" respectively.
On the other hand, Brian likes the word "node" for things in the filesystem because it emphasizes that the filesystem is a graph and that the thing at the end of an edge can be either a file or a directory, so if it fits continue to use "node" or "filesystem node" or some such to denote those things.
There's a new source:docs/install.html that is short and sweet.
But this means that all of the other details from README need to be rewritten into install-details.html.
I'm going to fix source:docs/install-details.html on the plane tomorrow.
source:docs/install.html is good. See #264 for further docs.