add basic service configuration #236
No reviewers
kiara
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.
Dependencies
No dependencies set.
Reference: fediversity/fediversity#236
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fricklerhandwerk/Fediversity:nested-forms-hack"
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?
Closes #73
@ -0,0 +1,112 @@from django import formsthe versioning references here follow the design at #229, so on that the same drawbacks would apply.
given this PR does not otherwise need that part tho, i would suggest splitting that out for now.
@ -0,0 +5,4 @@from django_pydantic_field import SchemaField# TODO(@fricklerhandwerk):# Eventually should probably maintain a separate series of configuration schema versions for each service.does this already separately store the application configs?
from @fricklerhandwerk: No, as noted I didn’t go into that yet to keep it flat for now
kiara referenced this pull request2025-03-12 16:33:23 +01:00
merging with #247 to unblock #246 while keeping some breathing room on the versioning question