pykgr
nix-prisma-example
pykgr | nix-prisma-example | |
---|---|---|
1 | 1 | |
0 | 27 | |
- | - | |
0.0 | 0.0 | |
about 2 years ago | 10 months ago | |
Python | Nix | |
BSD 3-clause "New" or "Revised" License | Apache License 2.0 |
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.
pykgr
-
The Curse of NixOS
Not being able to use it in a home directory without root was a major turn off for me. I actually started writing a python module to install packages in a way similar to nix (albeit I never got to reproducibility) but ran into problems building glibc and installing it to the home dir. I’d like to continue it one day.
https://github.com/DylanEHolland/pykgr
nix-prisma-example
-
The Curse of NixOS
For the system, I like the devos template:
https://github.com/divnix/devos
The idea of flakes is how you define inputs, and you define the system (and packages, and shell etc.) in the outputs using the inputs. The inputs are git repos which point to other flakes. You can mix and match these as much as you want (see the devos repo for examples) and when you build the derivation, it generates a lockfile for exact commits in that point in time what were used in the given inputs.
You commit the lockfile and in the other systems where you pull your config from the repo, it uses exactly those commits and installs the same versions as you did in your other systems.
This was quite annoying and hard to do before flakes. Now it's easy.
The problem what people face with building their system as a flake is combining the packages so you can point to `jq` from the unstable nixos and firefox from the stable train. I think this aspect needs better documentation so it wouldn't be so damn hard to learn (believe me, I know). Luckily there are projects like devos that give a nice template for people to play with (with documentation!)
Another use for flakes is to create a development shell for your repo, an example what I did a while ago:
https://github.com/pimeys/nix-prisma-example
Either have `nix-direnv` installed, enter the directory and say `direnv allow`, or just `nix develop` and it will gather, compile and install the correct versions of packages to your shell. Updating the packages? Call `nix flake update` in the directory, commit the lockfile and everybody else gets the new versions to their shell.
What are some alternatives?
aconfmgr - A configuration manager for Arch Linux
nixos-beginners-handbook - The missing handbook for NixOS beginners
star-history - The missing star history graph of GitHub repos - https://star-history.com
impermanence - Modules to help you handle persistent state on systems with ephemeral root storage [maintainer=@talyz]
digga - A flake utility library to craft shell-, home-, and hosts- environments.
asdf-nodejs - Node.js plugin for asdf version manager
nix-embedded - Nix embedded image generator.
nonguix
nixpkgs-config - ~/.config/nixpkgs