-
## Problem
In a world where CA derivations take over, this is a non-issue: the use of exclusively content-addressing store paths mean that we are effectively constructing merkle dags / doing deep c…
-
"realisation" is a bad term because we already use it for other things (building, including input-addressed derivations) and because it is vague.
The term in https://www.microsoft.com/en-us/researc…
-
This is for the stuff discussed in NixOS/rfcs#62. I believe there is enough consensus that we can continue doing this as an unstable feature, and return to the RFC when we want to stabilize it.
Per…
-
Supercedes #45
In this replication variant, pages are replicated based on their content hash. Thus the current state of the file can be computed from the content store (provides access to pages by…
-
One of the caveats in the documentation is:
> Absolute paths to files must match to get a cache hit. This means that even if you are using a shared cache, everyone will have to build at the same ab…
-
this gives us similar properties to arbitrary sized content addressed blocks
-
This idea attempts to allow for Content-addressed-style storage, but allows content to be encrypted such that only the possessor of the content's hash/identifier can read it. I expect this idea is not…
-
# Content addressed data access
## Why?
- To de-duplicate files between sites.
- Allow better site archiving
- Avoid data loss on site moderation/changes
## What?
Store and access base…
-
I've been meaning to try `deploy-rs` for my systems, but it turns out that it doesn't work if the closure to deploy contains some content-addressed derivations. For example given the following flake (…
-
A zfs content addressing layer, not too dissimilar to git's content addressing, is a simple _hero tier_ plugin enhancement for zfs filesystems.
It is simple since Git provides a well proven, and si…