issue-274 #278

Open
m wants to merge 14 commits from issue-274 into staging
Owner

Closes #274

Tasks

  • Create diagrams
  • Put hardcoded blossom sigit in the CONFIG.YML
  • When adding a Blossom server, send a request to check if it's a valid Blossom server, and check the "title" tag if it includes "Blossom Server"
  • Display spinners, and say status (validating blossom server, signing auth event, uploading to blossom.sigit.io)
  • When getting appData get from all Blossom servers
  • When the user adds Blossom servers, updateAppData will send user app data to all Blossom servers
  • In settings add the "servers" page to add preferred blossom servers, the default will be blossom.sigit.io
  • Use the sigit_design for settings
  • When servers are found in meta.json (zipUrls) use those servers just to read from it
  • Creator: when uploading files, we should try to write to all servers, and only put the successful ones in the meta.json
  • Add zipUrls to the meta.json - location of the encrypted zip files, it can be on multiple file servers
  • Start checking zipUrls and use the first which has the correct hash
  • Fetch sigits from all blossom servers and display them
  • When you open /verify/sigitId, show on which blossom URL was found
  • If not published to other Blossom urls, publish to all user-preferred Blossom servers, when the user hits SIGN
  • Max 3 blossom servers
  • test blossom branch against a fresh account
  • When open verify or sign page show on which blossoms is uploaded

Issues introduced by refactor

  • When multiple signer markConfig list does not include second signer marks - (happened only once)

Deployed version

https://test.sigit.io/

Diagrams

image

Closes #274 ### Tasks - [x] Create diagrams - [x] Put hardcoded blossom sigit in the CONFIG.YML - [x] When adding a Blossom server, send a request to check if it's a valid Blossom server, and check the "title" tag if it includes "Blossom Server" - [x] Display spinners, and say status (validating blossom server, signing auth event, uploading to blossom.sigit.io) - [x] When getting `appData` get from all Blossom servers - [x] When the user adds Blossom servers, updateAppData will send user app data to all Blossom servers - [x] In settings add the "servers" page to add preferred blossom servers, the default will be blossom.sigit.io - [x] Use the sigit_design for settings - [x] When servers are found in meta.json (zipUrls) use those servers just to read from it - [x] Creator: when uploading files, we should try to write to all servers, and only put the successful ones in the meta.json - [x] Add `zipUrls` to the meta.json - location of the encrypted zip files, it can be on multiple file servers - [x] Start checking `zipUrls` and use the first which has the correct hash - [x] Fetch sigits from all blossom servers and display them - [x] When you open /verify/sigitId, show on which blossom URL was found - [x] If not published to other Blossom urls, publish to all user-preferred Blossom servers, when the user hits SIGN - [x] Max 3 blossom servers - [x] test blossom branch against a fresh account - [ ] When open verify or sign page show on which blossoms is uploaded ### Issues introduced by refactor - [x] When multiple signer markConfig list does not include second signer marks - (happened only once) ### Deployed version https://test.sigit.io/ ### Diagrams ![image](/attachments/db4c7b94-a0b8-4ea3-a56d-a843e31f3c2f)
1.3 MiB
m added 2 commits 2024-12-17 20:11:13 +00:00
y reviewed 2024-12-18 05:28:46 +00:00
@ -0,0 +80,4 @@
// Check if new server is a valid URL
if (
!/^(https?:\/\/)(?!-)([A-Za-z0-9-]{1,63}\.)+[A-Za-z]{2,6}$/gim.test(
Owner

should be a utility

should be a utility
m marked this conversation as resolved
m added 2 commits 2024-12-18 15:19:41 +00:00
feat: added config.json and fileServerMap to the redux
All checks were successful
Open PR on Staging / audit_and_check (pull_request) Successful in 45s
3de5edfbf6
m added 1 commit 2024-12-23 11:29:25 +00:00
Merge branch 'staging' into issue-274
All checks were successful
Open PR on Staging / audit_and_check (pull_request) Successful in 43s
185f24c046
m added 3 commits 2024-12-23 13:03:31 +00:00
m added 2 commits 2024-12-30 16:26:23 +00:00
fix: lint type fix
All checks were successful
Open PR on Staging / audit_and_check (pull_request) Successful in 39s
d0d84a860f
m added 1 commit 2024-12-30 16:27:25 +00:00
Merge branch 'staging' into issue-274
All checks were successful
Open PR on Staging / audit_and_check (pull_request) Successful in 46s
6dab22a495
m added 2 commits 2025-01-02 09:49:52 +00:00
chore(git): Merge branch 'staging' into issue-274
All checks were successful
Open PR on Staging / audit_and_check (pull_request) Successful in 45s
18c07556ea
m added 1 commit 2025-01-02 12:32:30 +00:00
feat: maximum of 3 blossom servers
All checks were successful
Open PR on Staging / audit_and_check (pull_request) Successful in 38s
67d33e1aff
m changed title from WIP: issue-274 to issue-274 2025-01-02 16:39:27 +00:00
Author
Owner

It needs to be thoroughly tested: https://test.sigit.io

It needs to be thoroughly tested: https://test.sigit.io
All checks were successful
Open PR on Staging / audit_and_check (pull_request) Successful in 38s
This pull request can be merged automatically.
You are not authorized to merge this pull request.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin issue-274:issue-274
git checkout issue-274
Sign in to join this conversation.
No reviewers
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: sigit/sigit.io#278
No description provided.