In October, we released Determinate Nix and announced that private flakes and FlakeHub Cache are now generally available. FlakeHub authentication is often automatic, using cloud native mechanisms like JSON Web Tokens (JWTs) and Amazon Instance Metadata Service (IMDS), eliminating from your workflows cumbersome tasks like sharing credentials and manually rotating tokens.
As a stark alternative, Determinate Nix manages the lifecycle of these tokens by automatically synthesizing a netrc file that Nix can use to authenticate with FlakeHub. That means that your entire organization has a frictionless path to using features like FlakeHub Cache and private flakes.
Would you like access to private flakes and FlakeHub Cache?
Since that initial release, customers migrating to FlakeHub Cache have indicated that they want to read from their old cache during the transition. These customers are excited by FlakeHub Cache’s support for Single sign-on (SSO) and rotating per-user credentials but they still have static credentials to their fleet of machines shared amongst their teams. To serve these customers—any another potential FlakeHub users—we now support extending our synthesized netrc file with customer-defined entries, and we recently published a new guide for Migrating to FlakeHub Cache.
Sign up now at
