Skip to content
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

Open
wants to merge 6 commits into
base: main
Choose a base branch
from
Open

FlakeHub Cache docs #17

wants to merge 6 commits into from

Conversation

lucperkins
Copy link
Member

@lucperkins lucperkins commented Aug 7, 2024

No description provided.

Copy link

netlify bot commented Aug 7, 2024

Deploy Preview for flakehub-docs ready!

Name Link
🔨 Latest commit 70b8797
🔍 Latest deploy log https://app.netlify.com/sites/flakehub-docs/deploys/66ec0b138886640008dbd9b9
😎 Deploy Preview https://deploy-preview-17--flakehub-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@lucperkins lucperkins marked this pull request as ready for review August 12, 2024 13:35
pages/features/cache.mdx Show resolved Hide resolved
pages/features/cache.mdx Outdated Show resolved Hide resolved
No other authentication method, like public keys, is necessary.
* The [Magic Nix Cache Action][mnca]

<Callout type="info">
Copy link

@edolstra edolstra Sep 16, 2024

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.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants