sigit/sigit.io
7
2
Fork 0
Code Issues 31 Pull Requests 2 Actions Packages Projects 1 Releases Wiki Activity

Blossom Server Configuration #274

New Issue
Open
opened 2024-12-09 11:28:21 +00:00 by b · 4 comments
b commented 2024-12-09 11:28:21 +00:00
Owner
Copy Link

It should be possible to use multiple blossom servers for data storage

We need:

  • A menu in Settings to add and manage the blossom server array
  • To ensure that the application logic uses all the blossom servers in the array (for reading and publishing)

This page should also display the npub used for publishing

It should be possible to use multiple blossom servers for data storage We need: - A menu in Settings to add and manage the blossom server array - To ensure that the application logic uses all the blossom servers in the array (for reading and publishing) This page should also display the npub used for publishing
m was assigned by b 2024-12-09 11:28:35 +00:00
b commented 2024-12-09 11:39:44 +00:00
Author
Owner
Copy Link

When opening a SIGit (verify page), it should show on which blossom server(s) it was found (eg https://blossom_old.sigit.io)

For the ones where it was not found, there should be an icon to publish it to that server

When opening a SIGit (verify page), it should show on which blossom server(s) it was found (eg https://blossom_old.sigit.io) For the ones where it was not found, there should be an icon to publish it to that server
m commented 2024-12-10 15:56:25 +00:00
Owner
Copy Link

When visiting a SIGIT by a link that no longer has files from Blossom, we should display the metadata. Currently, the app breaks.

image

When visiting a SIGIT by a link that no longer has files from Blossom, we should display the metadata. Currently, the app breaks. ![image](/attachments/f917dbf2-3d4e-4926-8cdb-504757cc05d8)
image.png
105 KiB
m commented 2024-12-10 16:03:26 +00:00
Owner
Copy Link
image
<img width="984" alt="image" src="attachments/e211a224-f053-4574-8530-25aadcb0a2c6">
image.png
110 KiB
enes added this to the MVP project 2024-12-19 09:42:00 +00:00
b commented 2025-01-02 09:46:30 +00:00
Author
Owner
Copy Link
  • test task
- [x] test task
b moved this to In Progress in MVP on 2025-01-10 10:14:38 +00:00
b moved this to In Progress in MVP on 2025-01-10 10:16:00 +00:00
b moved this to In Progress in MVP on 2025-01-10 10:17:08 +00:00
enes moved this to In Progress in MVP on 2025-01-20 19:28:29 +00:00
enes moved this to In Progress in MVP on 2025-01-20 19:28:31 +00:00
enes moved this to In Progress in MVP on 2025-01-24 09:37:18 +00:00
enes moved this to In Progress in MVP on 2025-01-24 14:07:29 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Kind/Breaking
Breaking change that won't be backward compatible
Kind/Bug
Something is not working
Kind/Documentation
Documentation changes
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/Security
This is security issue
Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project MVP
Assignees
Clear assignees
No Assignees m
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sigit/sigit.io#274
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?