Explore >> Select a destination
|
You are here 
|
kokada.dev | ||
| | | | |
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... | |
| | | | |
fzakaria.com
|
|
| | | | | If you have used Nix flakes, you likely encountered something like the following. ?? std.url = "github:divnix/std"; std.inputs.devshell.follows = "devshell"; std.inputs.nixago.follows = "nixago"; std.inputs.nixpkgs.follows = "nixpkgs"; hive.url = "github:divnix/hive"; hive.inputs.colmena.follows = "colmena"; hive.inputs.disko.follows = "disko"; hive.inputs.nixos-generators.follows = "nixos-generators"; hive.inputs.nixpkgs.follows = "nixpkgs"; Why is this follows necessary? ?? It's in fact not necessary b... | |
| | | | |
msfjarvis.dev
|
|
| | | | | Quick how-to for writing ad-hoc checks for your own Nix Flakes | |
| | | | |
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. | ||
