-
Notifications
You must be signed in to change notification settings - Fork 2
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
FlakeHub Cache docs #17
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for flakehub-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
No other authentication method, like public keys, is necessary. | ||
* The [Magic Nix Cache Action][mnca] | ||
|
||
<Callout type="info"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not clear how this callout relates to the stuff above it. Probably we want to say something like "You can push your stuff to the cache using one of the following actions: magic-nix-cache
and Determinate CI" and then have subsections for each.
*FlakeHub Cache* is a [Nix binary cache][cache] that works in conjunction with [FlakeHub][home]. | ||
It has two main features that distinguish it from other Nix caching services: | ||
|
||
1. It enables you to [control access](#access-control) at the [flake][flakes] level. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IIRC the access control is at the repository level. If you have one flake per repo that's the same thing, but you could be releasing multiple flakes from the same repo, and they would share the same cache by default.
No description provided.