nix-embedded
nixpkgs-config
nix-embedded | nixpkgs-config | |
---|---|---|
1 | 15 | |
2 | 140 | |
- | - | |
0.0 | 6.2 | |
almost 3 years ago | 4 months ago | |
C | Nix | |
- | - |
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-embedded
-
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
nixpkgs-config
-
Diving straight into flakes with no channels?
You can also take a look at my server configuration which uses flakes. And my separately-managed home-manager configuration which also uses flakes
-
So I’m hooked on this declarative configuration business. How deep does the rabbit hole go? Can I “rice” my desktop with just one file?
My "rice": https://github.com/jonringer/nixpkgs-config
-
libstdc++.so.6 => not found
I configure my neovim through home-manager. My configuration. Pulling vimPlugins from nixpkgs should give you something which works with NixOS (or anywhere for that matter, NixOS is essentially a clean room).
-
A Cross-Platform tool to deploy dot files
My dot file repo.
-
Using NixOS and Arch on separate machines
Home-manager link My example setup
-
Neovim unstable
Reference: - home.nix entry - Which refers to it's own dedicated file
- should i move all my pkgs from configuration.nix and move to home manager?
-
Installing every Arch package
If you want to take nix for a spin, i would recommend trying home-manager. It's essentially NixOS, but for dot files. It can install packages and services in addition to manage configuration. Also, I've been able to get it work on NixOS, WSL2, ubuntu, and macOS. Personal configuration if you're curious how it would look.
-
The Curse of NixOS
> And about Home Manager, the reason why I think it's over-hyped is because it provides a declarative approach to something that was... already declarative. Your $XDG_CONFIG directory does not need a leaky Nix abstraction on top of it
I don't really agree, I spent about 30mins to get my home-manager config to support an m1 mac [0]. I don't really want to think how long it would take me to look up all of the homebrew package names, and learn a new package manager. Instead, I just pushed all of the linux-specific items into their own bin, a little more logic, and I was able to get back to a comfortable terminal + git + vim settings.
Also, nix exposes congruent configuration management[1]. The state of my system is an exact reflection of the configuration. With other tools like ansible, vagrant, etc, I would get reconciliation configuration which is close on initial install but configuration drift is an ever-present concern; not to mention that large recipes and playbooks can take a very long time to run. Going the homebrew route would be divergent configuration, it would be very hard for me to get back to a certain configuration. With nix (and by extension home-manager), I can version control the configuration, improve it, roll it back, w/e I want.
> Why would I write my i3 config in Nix??
You do get some type checking, although the iteration time would probably be similar. You could also just do `xsession.windowManager.i3.extraConfig = builtins.readFile ./i3.config;` if you really just wanted to wholesale read in your existing profile.
> I'd rather just use `nix-env` personally.
nix-env is a double edge sword. You can rollback (somewhat, I believe it's just a stack of all changes), which is an improvement. However, nix only retains the "derivation name" to try and management. But for packages like python38, if you try to upgrade it, it will determine that `python-3.11-a3` is the package which is the most up-to-date. I try to discourage using nix-env.
[0]: https://github.com/jonringer/nixpkgs-config/commit/37ddfefa1...
-
Where are alacritty and systemd specified to install?
Here and full config here
What are some alternatives?
impermanence - Modules to help you handle persistent state on systems with ephemeral root storage [maintainer=@talyz]
base16-nix - Home manager module for themeing programs with base16 templates
nix-fpga-tools
eww - ElKowars wacky widgets
nixos-beginners-handbook - The missing handbook for NixOS beginners
nix-prisma-example - An example Prisma project using nix
aconfmgr - A configuration manager for Arch Linux
nix-config - Personal NixOS configuration
star-history - The missing star history graph of GitHub repos - https://star-history.com
rfcs - The Nix community RFCs
wallpaper-generator - Generate wallpaper images from mathematical functions