facilitate use without flakes #518
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.
Depends on
#528 retire
flake-parts
fediversity/fediversity
Reference: fediversity/fediversity#518
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?
ideally, one should not need to use flakes to be able to run our code.
flake as thin wrapper over attributes exposed through
default.nix.currently some tests are exposed only through our flake - in part perhaps due to nixops4's use of
flake-partsmaking it harder to de-flake (c.f. https://github.com/nixops4/nixops4/issues/113).to facilitate lazily-loaded scripts (like flakes'
apps), i might try and use separate shells.flake-partsflake as thin wrapper over attributes exposed throughto facilitate use of fediversity without flakesdefault.nixfacilitate use of fediversity without flakesto facilitate use without flakes_module.argstospecialArgs#486