Closed srid closed 4 years ago
I just tested this as well.
You need to follow instructions by clicking "getting started" while on cachix.org, step (4) generates the keypair.
Any suggestions on how to make this better UX, what have you missed?
Ah, okay. It wasn't clear to me (possibly this is what tripped up @srid as well) that the signing key was generated by step 4. I think the UX could be improved by making this more explicit, because i was under the assumption that just hitting 'create' would get me one.
Thanks!
Thanks, I'll address this.
Any suggestions on how to make this better UX, what have you missed?
I think in the action's README instead of saying "Login to Cachix and create a new cache. Backup the signing key in the process." if it said something like "Login to Cachix, create a new cache and run cachix generate-keypair <cachename>
and write down that signing key." that would have been straightforward.
I think other source of potential confusion is that in the UI it says "keypair" but in the Action readme it says "signing key".
Instead of fixing README, I'll make sure the flow of cachix.org is clear.
Thanks for the keypair hint, I'll think about how to solve that one.
https://nix.dev/tutorials/continuous-integration-github-actions.html#creating-your-first-binary-cache is now more specific and the new text that I'll deploy soon will improve the wording to be about the signing key.
In the README it says,
In cachix.org however when I create a new public cache no such 'signing key' is displayed.