Generate documentation on the deployments from the code #89
Labels
No labels
api service
blocked
bug
component: fediversity panel
component: nixops4
documentation
estimation high: >3d
estimation low: <2h
estimation mid: <8h
productisation
project-management
question
role: sysadmin
security
technical debt
testing
type unclear
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
#288 external developers empowered to contribute}
Fediversity/Fediversity
Reference: Fediversity/Fediversity#89
Loading…
Add table
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?
Right now the README hardcodes how machines are used and for which deployments. This will go out of date very quickly.
We already have this information as structured data being used for the actual deployments right there in our source code. Generate the README from that code, e.g. using a pre-commit hook that is backed by a CI check
Niols referenced this issue2025-02-25 12:18:53 +01:00
i think deployments should not be hard-coded into our code-base, nor their documentation
What I meant here is our infrastructure setup, not the deployments we run for (even demo) operators. Currently it's a table with which machines are used for what, and since we have that in an expression, we may as well render that into a more easily human-readable table instead of writing it down.
Note that this is of course a very low-priority QoL issue.