-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
a single additional cache is not enough #545
Comments
Having many read caches and one write cache would be really awesome, I think with current arch this would be very simple to implement |
In addition, hard-coding it to |
x-ref: input-output-hk@3cd7dc0 BTW, I absolutely love how all cache config is totally self-contained. |
Good news is that we will get to the point where you won't have to fork I'll try to merge those features upstream so the entire ecosystem benefits from this feedback, |
@blaggacao your feedback would be very appreciated: https://github.com/fluidattacks/makes#cache |
Ok, gotta schedule it for after lunch. ⌛ |
What do you think about making
|
@kamadorueda Also, is there a specific reason for not including all
Also, Is priority being considered here? |
caches priority is defined by the cache itself, for example: https://cache.nixos.org/nix-cache-info (40) and https://fluidattacks.cachix.org/nix-cache-info (41) |
That's nice, though we don't use that data so that's why I didn't include it, also, there are code comments if people feel the need of adding such information
yes, the reason is that we only support read+write on cachix, whereas read caches can be anything from cachix, to hydra, to S3 buckets, anything over HTTP the read protocol is standardizes, whereas the write protocol is not |
In my scenario, I got:
The text was updated successfully, but these errors were encountered: