modify gridsync to work with magic-folder #2714
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
2 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#2714
Loading…
Reference in New Issue
Block a user
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?
Gridsync is a Qt shell for the Tahoe-LAFS install and run procedures. It's GUI wraps various Tahoe-LAFS CLI commands so that the user can click through an easy to use install wizard to configure their Tahoe-LAFS client... and then run it.
https://github.com/gridsync/gridsync
This ticket shall be resolved when gridsync utilizes the new magic-folder CLI commands such that the user of this dev branch of gridsync could easily click through a wizard that sets up their Tahoe-LAFS client + magic-folder.
Upon a reviewing the gridsync source code this task appears to be easy because fundamentally it's a shell that runs Tahoe CLI commands in it's own process; it happens to be a twisted app the uses the Qt Reactor.
The additional GUI features that gridsync may need to display realtime status updates will not be included in this ticket.
For what it's worth, I've cross-posted this ticket as a Github issue here: https://github.com/gridsync/gridsync/issues/25