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

Blossom - Tidy Up Sigit Blossom Versioning #211

New Issue
Closed
opened 2024-09-18 15:26:26 +00:00 by eugene · 3 comments
eugene commented 2024-09-18 15:26:26 +00:00
Owner
Copy Link

The Sigit Blossom fork on the server is out of sync and diverged from the main blossom server repo. We should fix that.

Also, should we deploy our blossom-server fork on Gitea and mirror our github fork?

The Sigit Blossom fork on the server is out of sync and diverged from the main blossom server repo. We should fix that. Also, should we deploy our blossom-server fork on Gitea and mirror our github fork?
m was assigned by b 2024-11-26 09:56:28 +00:00
m commented 2024-11-26 09:57:51 +00:00
Owner
Copy Link

Update

Blossom includes Dockerfile in the original repo, we should check if it's possible to discard our forked one and just use the original.

Main task is to check if new Blossom version can reuse our existing data

## Update Blossom includes Dockerfile in the original repo, we should check if it's possible to discard our forked one and just use the original. Main task is to check if new Blossom version can reuse our existing data
b commented 2024-12-02 09:53:22 +00:00
Owner
Copy Link

plan would be to migrate to a cloudron blossom instance

plan would be to migrate to a cloudron blossom instance
b commented 2024-12-31 09:50:47 +00:00
Owner
Copy Link

done

done
b closed this issue 2024-12-31 09:50:47 +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
Assignees
Clear assignees
No Assignees m
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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