3 ms·
It's sounds like one of the major problems here was using configuration.nix. Nix flakes provide a much better user experience, but they are currently "experimen
by zamalek 3y ago
It's sounds like one of the major problems here was using configuration.nix. Nix flakes provide a much better user experience, but they are currently "experimental" (seriously, its time to stabilize flakes) and you are not guided to use them at all.
I have .envrc ignored in my global gitignore, and then I write 'use flake $HOME/my-nix-config#node' to .envrc. direnv then grabs that and does the rest. I no longer need to commit anything Nix related to git, so my coworkers are none the wiser.
Ultimately this article shows that, once again, the problem with Nix is the documentation.
- nathanckim18 3y agoOh wow, that's a very neat config and one that I wish I had thought of, my main pain point was in trying not to clog up collaboration environments. Thanks for sharing!