flakelight
Framework for simplifying flake setup [maintainer=@accelbread] (by nix-community)
hackernews-docker-challenge
By max-privatevoid
flakelight | hackernews-docker-challenge | |
---|---|---|
1 | 1 | |
157 | 1 | |
13.4% | - | |
9.0 | 6.3 | |
10 days ago | about 2 months ago | |
Nix | Java | |
MIT License | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
flakelight
Posts with mentions or reviews of flakelight.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-03-15.
-
Nix is a better Docker image builder than Docker's image builder
There are attempts like
https://flake.parts/
or
https://github.com/nix-community/flakelight
Their aim is to create an ecosystem of reusable Nix libraries. But it is tiny.
hackernews-docker-challenge
Posts with mentions or reviews of hackernews-docker-challenge.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-03-15.
-
Nix is a better Docker image builder than Docker's image builder
There's not much else that can be done here. glibc is the next largest dependency at ~30MB. This large size seems to be because Nixpkgs configures glibc to be built with support for many locales and character encodings. I don't know if it would be possible or practical to split these files out into separate derivations or outputs and make them optional that way. If you're using multiple images built by dockerTools.buildLayeredImage, glibc (and everything else) will be shared across all of them anyway (given you're using roughly the same Nixpkgs commit).
https://github.com/max-privatevoid/hackernews-docker-challen...