Explore >> Select a destination
|
You are here 
|
jvns.ca | ||
| | | | |
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.haskellforall.com
|
|
| | | | | Announcing nixos-rebuild: a "new" deployment tool for NixOS The title of this post is tongue-in-cheek; ni... | |
| | | | |
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. | |
| | | | |
myme.no
|
|
| | | |||
