Configure applications #610
kiara
commented
Owner
- #158 #195 #627 #628 #213 #214 Configuration uses a batteries-included approach.
- [app-specific] #629 Relevant configuration options are available for operators to tweak, presented using a user-friendly web interface, that further aid the user in case updates change the available options.
<!-- Applications may be complex enough to warrant not using a one-size-fits-all approach. -->
1. #158 #195 #627 #628 #213 #214 Configuration uses a batteries-included approach.
<!-- 1. #158 #195 #627 As such, relevant configuration options should be made available for operators to tweak,
#628 presented using a user-friendly web interface,
#213 #214 that further aid the user in case updates change the available options. -->
1. [app-specific] #629 Relevant configuration options are available for operators to tweak, presented using a user-friendly web interface, that further aid the user in case updates change the available options.
<!-- Nevertheless, we should default to a batteries-included approach, applying sane defaults such that only power users should need to access any advanced settings. -->
<!-- #629 including on updates. -->
kiara
added the type: key result
label
kiara
added a new dependency
#158 users can update their deployment configurations
kiara
added a new dependency
#195 NixOS modules' options exposed
kiara
added a new dependency
#289 key features improving user experience supported
kiara
added a new dependency
#627 expose applications' configuration options
kiara
added a new dependency
#629 schema updates automated
kiara
added a new dependency
#628 render option forms
kiara
added a new dependency
#214 aid needed actions on schema update
kiara
added a new dependency
#213 visualise schema changes
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
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
#289 key features improving user experience supported
fediversity/fediversity
#158 users can update their deployment configurations
fediversity/fediversity
#195 NixOS modules' options exposed
fediversity/fediversity
#213 visualise schema changes
fediversity/fediversity
#214 aid needed actions on schema update
fediversity/fediversity
#627 expose applications' configuration options
fediversity/fediversity
#628 render option forms
fediversity/fediversity
#629 schema updates automated
fediversity/fediversity
Reference: fediversity/fediversity#610
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?