Global Dev Setupįor installing tools globally, I've read about nix profiles, but I was unsure about how to use them with Flakes. I have read that flakes and nix are still considered alpha but from my perspective right now it feels 95% done - and maybe other projects would have called this a finished product by now. Only go declarative: I will never install a package by typing a CLI command, but always editing some configfile and running a "converge" script.It seems the new world and the old world sometimes are incompatible, and you need to decide which way to go consistently. Only use the nix tool, instead of the older nix-env etc tools.Embrace Nix Flakes: I'll only use nix flakes, especially after reading this blog post.When reading about the ecosystem, I saw there are lots of patterns how one could use Nix and this is in flux right now, as the community irons out flakes (which many people seem to be using already though). I also checked out jetpack-io/devbox which does fundamentally the same thing but which hides the Nix files completely underneath - so that was too restrictive for my tastes. have reproducible dev environments (basically replacing docker)įor the second use case, reproducible dev environments, I quickly settled on cachix/devenv.have a reproducible global dev tool setup (basically a replacement for Homebrew).For installing, I used the unofficial installer DeterminateSystems/nix-installer for reasons explained on the website, which ran through smoothly.Īfter doing the tutorials at, I wondered how to continue. I started by reading all of - a great website which explains the first baby steps. I by no means understand Nix fully yet, but making progress and it is usable to me already. This was on my agenda since a long time, but I finally took the plunge on my M1 OSX system. I finally had some time to play around with Nix - the immutable package manager and build system.
0 Comments
Leave a Reply. |