nix-prisma-example
nvd
nix-prisma-example | nvd | |
---|---|---|
1 | 4 | |
27 | - | |
- | - | |
0.0 | - | |
10 months ago | - | |
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.
nvd
-
First post, here's my home lab and how I use it every day (running Proxmox and NixOS)
And this repo:https://gitlab.com/khumba/nvd
-
The Curse of NixOS
There's nothing there that needs flakes (an experimental feature which people should not enable without understanding the implications). You could build a system derivation and run a diff against /run/current-system on it.
For what it's worth, nix-diff has very verbose output (it literally diffs everything that is different in the inputs & outputs). A slightly nicer way to diff systems is nvd[0] (example output[1]) which only shows version changes and added/removed packages.
[0]: https://gitlab.com/khumba/nvd
[1]: https://deploys.tvl.fyi/diff/4xmyvkr9nw0cwkn5q38p0cfc58x3jdy...
- Nix/NixOS package version diff tool
-
Can I see what packages have been updated?
And it uses https://gitlab.com/khumba/nvd to diff the revisions
What are some alternatives?
nixos-beginners-handbook - The missing handbook for NixOS beginners
nix-config - Mirror of http://chriswarbo.net/git/nix-config
impermanence - Modules to help you handle persistent state on systems with ephemeral root storage [maintainer=@talyz]
jk - Configuration as Code with ECMAScript
star-history - The missing star history graph of GitHub repos - https://star-history.com
nixos-config - Nix configuration for macOS / NixOS with starter templates, step-by-step guides, and more ✨
asdf-nodejs - Node.js plugin for asdf version manager
nix-fpga-tools
aconfmgr - A configuration manager for Arch Linux
nix-helpers - Mirror of http://chriswarbo.net/git/nix-helpers.git
nixpkgs-config - ~/.config/nixpkgs