Explore >> Select a destination
|
You are here 
|
drakerossman.com | ||
| | | | |
rgoswami.me
|
|
| | | | | A short exploration of multi-user nix and interacting with the Nix User Repository without root Background For multi-user nix installations1, the NIX_PATH variable is empty. Here I briefly go over two approaches to mitigate this, one with nix-channel and the other by manual pinning. Note that this post will eventually be superseded for most cases by a better flake workflow. Channels The idea behind using a channel is essentially that the tar at a particular commit / tag will be downloaded and stored, typically at $HOME/.nix-defexpr/channels. This is in-fact a symlink typically as seen below. | |
| | | | |
ianthehenry.com
|
|
| | | | | Okay. In the last post I got sort of an introduction to flakes, and I even wrote a flake, but I didn't learn how to... do anything with flakes. My flake provided an overlay, but I have no idea how to make my Nixpkgs actually use that overlay. I have no idea what "my Nixpkgs" even means anymore. My channel? My flake? Everything I've learned about Nix has been turned upside down. But presumably if we keep reading, these blog posts will explain how to actually put them to use. | |
| | | | |
tonyfinn.com
|
|
| | | | | Nix Flakes can be used for more than just package definitions. This post covers how you can define a development environment in a Nix flake. | |
| | | | |
www.thedigitalcatonline.com
|
|
| | | A blog featuring in-depth posts about Python, Scala, TDD, devops, security and all things development | ||
