Explore >> Select a destination
|
You are here 
|
www.zombiezen.com | ||
| | | | |
stephank.nl
|
|
| | | | | ||
| | | | |
thedroneely.com
|
|
| | | | | The Linux distribution space is vast and fragmented. It's the wild wild west, and that's all right in my book. | |
| | | | |
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. | |
| | | | |
blog.thalheim.io
|
|
| | | In this article, I will explain how to perform full integration tests with flakes outside nixpkgs. With NixOS testing framework, you can create end-to-end integration tests easily. It all comes down to starting a virtual machine based on your custom modules and testing its state with a Python script. This way, you can identify in advance all the regressions and incompatible configurations arising from the updates you introduced. One of the framework's upsides is that it's extremely fast - maybe the faste... | ||
