purenix
digga
Our great sponsors
purenix | digga | |
---|---|---|
4 | 23 | |
281 | 977 | |
4.6% | 0.4% | |
2.1 | 2.4 | |
3 months ago | 8 months ago | |
Haskell | Nix | |
BSD 3-clause "New" or "Revised" License | MIT License |
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.
purenix
-
Nix: An idea whose time has come
There’s also the PureNix project that lets you go from PureScript→Nix. Caveats in the docs.
- The Curse of NixOS
digga
-
Looking for dotfiles repo examples
I am using the home-manager input define in the flake andas recommended by digga. I am using the home namespace:
I have been playing with digga for a few days in order to simplify my dotfiles repo. But I only got it half-working and there are little to no - useful - docs.
This one issue may clear things up, seems like my config is a little outdated: https://github.com/divnix/digga/pull/385
-
Building a highly optimized home environment with Nix
I'm new to the Nix world, but so far I've come across Divnix's Digga, Numtide's DevShell, and Misterio77's nix-starter-configs.
-
Need for a configuration framework?
There are config templates / configuration helper libraries that try to make this easier, for example digga/devos.
-
Sharing configuration between NixOS and MacOS
The digga library, while being more complex to use than other solutions here, got a pretty elegant solution for it merged a few weeks ago. Still some cracks that are getting smoothed over, but it seems to work.
-
Best practices for organizing code repository for multiple machines? What about deployment?
I like the concept digga/devos uses (unfortunately their stuff kind of is an overengineered incomprehensible mess): They use: - modules: for modules like in nixpkgs (i.e. stuff that defines options and generates configuration based on that options; are included into every host) - profiles: concrete configuration, can be included to host definitions - suites: sets of profiles (so you can for example have a desktop suite with all your profiles with "desktop" configuration options and apply that to all your desktop computers)
- Nix: An idea whose time has come
-
The Curse of NixOS
https://github.com/divnix/devos is something close to a framework.
I agree that language is too simple. Also I think some degree of IDE / language server support would help a lot. Refactoring modules, writing and importing custom functions was a bad experience for me - some arcane stacktraces were common, using repl was too verbose and with no clear way to debug whole configuration.
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?
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
nixos-config - Mirror of https://code.balsoft.ru/balsoft/nixos-config
nixos - My NixOS Configurations
sops-nix - Atomic secret provisioning for NixOS based on sops
nix-darwin - nix modules for darwin
nixos-generators - Collection of image builders [maintainer=@Lassulus]
nixos - A fully automated replicable nixos configuration set
flake-utils-plus - Use Nix flakes without any fluff.
nix-home-manager - Nix to manage my computing life
nixos-config - My NixOS configurations.
nix - Nix, the purely functional package manager
onyx - Toolkit for converting and building songs for Rock Band, Guitar Hero, Clone Hero, and other similar rhythm games