button to create a new tiddly_on_tahoe instance #1317
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#1317
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?
With the current version of tiddly_on_tahoe, there is a bit of "manual labor" or "hassle" in the setup phase -- you have to create a Tahoe dir, then upload the TW wiki.html file to it, then edit the URL manually to append /wiki.html to the directory's URL.
tiddly_on_tahoe could do all of those steps automatically, at the press of a single button! It could issue a REST command to its host to create a new directory and then save a copy of itself to that directory. Once this is implemented, then there will be a single button that you can press to produce a clone of a given tiddly_on_tahoe instance. The new clone and the original will live in separate Tahoe directories, which means access to them can be separately granted or withheld. One could even imagine that this makes tiddly_on_tahoe into a "viral" decentralized web app, where it is trivial for unsophisticated users who look at one and like it to acquire their own.
Is that not cool? I think that would be awesome. Someone should definitely do it.
But not me, right now, as I really need to finish Repairer for Tahoe-1.3.0 ASAP.