code-based data model #103
Labels
No labels
0 points
0.5 points
1 point
13 points
2 points
21 points
3 points
34 points
5 points
55 points
8 points
api service
blocked
component: fediversity panel
component: nixops4
documentation
estimation high: >3d
estimation low: <2h
estimation mid: <8h
infinite points
productisation
project-management
question
role: application developer
role: application operator
role: hosting provider
role: maintainer
security
technical debt
testing
type unclear
type: bug
type: deliverable
type: key result
type: objective
type: task
type: user story
user experience
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Blocks
Depends on
#78 Start deployment migration
fediversity/fediversity
#100 migrating application data between hosting providers
fediversity/fediversity
#433 deployment provisions host infra
fediversity/fediversity
#491 port code to use the data model
fediversity/fediversity
#494 data model used
fediversity/fediversity
#105 finalize migration data model requirements
fediversity/fediversity
Reference: fediversity/fediversity#103
Loading…
Add table
Add a link
Reference in a new issue
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?
The data model should describe the migration process for #100 following the data model requirements:
implementation notes
this would cover entities:
#402#437[ ] type - branchbranchwip branchmigration (#100) - branchkiara referenced this issue2025-07-03 13:57:32 +02:00
applications.mastodonas a sample use-case of our data model #439I think we should split this into deployment data model (almost done) and migration data model (still needs research).
code-based migration data modelto code-based data model