Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/ners/nix-monitored
A transparent wrapper around Nix that pipes its output through Nix Output Monitor
https://github.com/ners/nix-monitored
nix nix-darwin nixos
Last synced: 17 days ago
JSON representation
A transparent wrapper around Nix that pipes its output through Nix Output Monitor
- Host: GitHub
- URL: https://github.com/ners/nix-monitored
- Owner: ners
- License: mit
- Created: 2022-12-22T08:00:59.000Z (almost 2 years ago)
- Default Branch: master
- Last Pushed: 2024-05-06T17:35:34.000Z (6 months ago)
- Last Synced: 2024-10-12T00:24:04.054Z (about 1 month ago)
- Topics: nix, nix-darwin, nixos
- Language: C++
- Homepage:
- Size: 46.9 KB
- Stars: 19
- Watchers: 3
- Forks: 3
- Open Issues: 3
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# nix-monitored
Pipe Nix through Nix Output Monitor without hassle.
## Motivation
Everyone I know wants to have nom's pretty output, but no one I know remembers to put `|& nom` after every command.
Further, nix-monitored can integrate with direnv and nixos-rebuild, which is difficult to do without overriding the Nix package.
### Shouldn't this be a shell script / `wrapProgram` / etc.?
The reasons it is C++ rather than a shell wrapper are:
- It runs on every Nix invocation, so overhead should be minimal.
- Building C++ is trivial with `stdenv`.
- Nix itself is written in C++, so it should be easier to maintain.
- Bash is notoriously terrible with string / parameter manipulation. The first version of this wrapper was Bash, and I kept running into weird string splitting errors, despite using `"$@"`.
### Shouldn't this be upstreamed into Nix?
I don't think so.
The Nix project has a stated mission of having low a runtime and dependencies. That's why it was authored in C++ and not something more respectable like Haskell. This design goal makes Nix attractive in a wide range of applications, e.g. on embedded devices with limited resources.
Nix Output Monitor does not share this design goal, and is therefore more resource heavy. In fact introducing any kind of fanciness in the Nix CLI, even with C++ or Rust, would likely increase Nix' runtime and dependency footprint.
With a wrapper like this, we can have our cake and eat it too: Nix stays appreciably small, but we can still use Nix Output Monitor on developer workstations if we wish. It's a win-win.
## Usage
On NixOS and nix-darwin, simply replace your `nix.package`, like so:
```nix
nix.package = pkgs.nix-monitored;
```
To make it work with `nix-direnv` and `nixos-rebuild`, we can override those packages:
```nix
nixpkgs.overlays = [
(self: super: {
nixos-rebuild = super.nixos-rebuild.override {
nix = super.nix-monitored;
};
nix-direnv = super.nix-direnv.override {
nix = super.nix-monitored;
};
})
];
```
If you're feeling adventurous, you can also simply try to override the Nix package entirely:
```nix
nixpkgs.overlays = [
(self: super: {
nix = super.nix-monitored.override {
inherit (super) nix;
};
})
];
```
A PR is in the works to bring this to NixOS as a module: [NixOS/nixpkgs#207108](https://github.com/NixOS/nixpkgs/pull/207108).
## Does it work?
The wrapper should work at least with the following tools:
- nix commands on the CLI, with and without flakes
- nix-direnv
- nixos-rebuild
It's been tested on both NixOS and macOS.