set default value for nixops4Package #412
No reviewers
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
ambition
application-offering
ambition
configure-applications
ambition
front-end
ambition/install-applications
ambition
security
ambition
switch-host
ambition
update-applications
ambition
user-management
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
3 participants
Notifications
Due date
No due date set.
Blocks
#389 Add
forgejo-ci machine to our infrastructure
fediversity/fediversity
Reference
fediversity/fediversity!412
Loading…
Reference in a new issue
No description provided.
Delete branch "kiara/fediversity:default-nixops-package"
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?
forgejo-cimachine to our infrastructure@ -150,0 +160,4 @@;inherit (inputs) nixops4;in(load-flake nixops4).packages.${pkgs.system}.default;why don't we instead splice it in through the overlay? it will reduce to
pkgs.nixops4here, source wrangling will happen inpanel/default.nix(before we merge it withdefault.nix) where it belongs, and the overlay is the correct place to add additional stuff topkgs.PS: IMO
../.is a code smell in the Nix language, and I recommend using it as an indicator to reconsider where to put things and how to pass them through.thanks, i moved it to the overlay now.
on paths like that, agreed (see #346). in this case tho, given the path targets the root-level flake path, what would you propose?
I'd propose to gradually rework the whole setup, as discussed last week; essentially modularize everything, just not with flake-parts, because there's no reason whatsoever to produce flake outputs. But there's very good reason to pass around values through module options and have some type safety (both for reducing opportunity for error and readability).
fb8957eb8633bc802c21Nice, clean change :)
Amazing!