Skip to content
Snippets Groups Projects
Commit e95b732f authored by Chris Wood's avatar Chris Wood
Browse files

Update "consuming" phase; remove node-running step

parent 688c5b7f
No related branches found
No related tags found
1 merge request!1Add "lightweight design" doc in markdown format
......@@ -182,12 +182,11 @@ From the user's perspective, the functionality of consuming the invite is achiev
Upon scanning the QR code, the software should perform the following actions
1. Validate the decoded contents of the QR code (i.e., to ensure that it contains the expected/valid grid connection information and a devicecap), displaying an error message if validation fails
2. Store the decoded contents of the QR code locally (e.g., in the app-specific storage directory)
3. Configure a local Tahoe-LAFS client node using the grid connection information obtained above
4. Launch the Tahoe-LAFS client node configured above and connect to the grid
5. Initiate an HTTP request to the locally-running Tahoe-LAFS WAPI to fetch the remote magic-folder contents (e.g., `GET /uri/$devicecap/v1/.magic-folders/` to list magic-folder names, `GET /uri/$devicecap/v1/.magic-folders/$name (personal)` to list magic-folder content)
6. Populate the file-browser/list-view using the JSON content returned in the body of the HTTP request(s) above
1. Validate the decoded contents of the QR code (i.e., to ensure that it contains the expected/necessary grid configuration values and a devicecap), displaying an error message if validation fails
2. Store the necessary configuration values decoded from the QR code locally (e.g., in the app-specific storage directory)
3. Supply the necessary configuration values to the local Tahoe-LAFS client as needed
4. Use the configured Tahoe-LAFS client to fetch the remote magic-folder contents (e.g., `GET /uri/$devicecap/v1/.magic-folders/` to list magic-folder names, `GET /uri/$devicecap/v1/.magic-folders/$name (personal)` to list magic-folder content)
5. Populate the file-browser/list-view using the JSON content returned in the body of the HTTP request(s) above
**Data integrity**
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment