nix-prisma-example
| nix-prisma-example | nix-fpga-tools | |
|---|---|---|
| 1 | 2 | |
| 27 | 20 | |
| - | - | |
| 0.0 | 2.6 | |
| 10 months ago | over 2 years ago | |
| Nix | Nix | |
| 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.
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.
nix-fpga-tools
-
Nix: An idea whose time has come
I would be surprised if there are any binaries that are outright impossible to run under Nix. I spent a weekend getting Xilinx ISE to run in Nix [0], that is a binary behemoth. It uses bubblewrap (already used in Nixpkgs) to setup a bunch of bind mounts so that the binaries see a standard FHS Linux layout.
[0] - https://github.com/benpye/nix-fpga-tools
-
The Curse of NixOS
Yeah I agree here, I used to find Nix somewhat unintuitive but I have now managed a few non-trivial projects. One being to package Xilinx ISE as a flake [0], and another to build a non-volatile Linux image using busybox and runit [1]. For the latter I still haven't quite gotten where I want but that's because I realised I needed dbus for avahi and dbus is just so ridiculously complex.
[0] - https://github.com/benpye/nix-fpga-tools/
[1] - https://github.com/benpye/nix-embedded
What are some alternatives?
nixos-beginners-handbook - The missing handbook for NixOS beginners
devshell - Per project developer environments
impermanence - Modules to help you handle persistent state on systems with ephemeral root storage [maintainer=@talyz]
star-history - The missing star history graph of GitHub repos - https://star-history.com
nix-helpers - Mirror of http://chriswarbo.net/git/nix-helpers.git
asdf-nodejs - Node.js plugin for asdf version manager
nix-embedded - Nix embedded image generator.
aconfmgr - A configuration manager for Arch Linux
nvd
nixpkgs-config - ~/.config/nixpkgs
nixpkgs - Nix Packages collection & NixOS