Flake for declarative installation through nix - #212
Open
JJJHolscher wants to merge 2 commits into
Open
Conversation
Contributor
|
@JJJHolscher Thank you for suggesting this. For this one, I am going to need @Myllaume to have a look. I will ping you here when we get to it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
By placing this flake.nix and flake.lock in the root of your repo, nix users can run it through
or install it inside their
flake.nixfiles.Maintenance?
If your build process changes, the
flake.nixmight break.nixis good at pinning to older versions though, so users won't suddenly stand in the cold. Me or any LLM will be able to restore the flake to function.Security?
flake.lockwill gradually age. Nix users would be advised to override the nixpkgs input, which isn't an uncommon practice. But by default, if some big security gap is found in node then patches won't propagate to users. I think this is a non-issue given the nature of cosma, but I don't mind setting a bi-yearly alarm so I update the flake.lock here (all it'd involve is runningnix flake updateand committing the new flake.lock)Of course, if you'd rather not have tools here that you don't use yourself then I understand that very well.