cache reusable computations #561
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
#224 automated dev-ops workflows
fediversity/fediversity
Reference: fediversity/fediversity#561
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?
some of the components we build can be used in different places, including production vs (different) tests.
to save on build time, it may be of interest to deduplicate such computations by reusing cached results when possible.
i think flakes may offer this using their
selffixpoint, which may be made available more widely using the likes offlake-parts(which.. we otherwise had mixed feelings toward, see #528).as such, we may want to:
as per Robert, Nix does not offer this yet.