InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now. Learn more →
Niv Alternatives
Similar projects and alternatives to niv
-
-
InfluxDB
InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.
-
-
age
A simple, modern and secure encryption tool (and Go library) with small explicit keys, no config options, and UNIX-style composability.
-
-
nix-direnv
A fast, persistent use_nix/use_flake implementation for direnv [maintainer=@Mic92 / @bbenne10]
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
-
anarki
Community-managed fork of the Arc dialect of Lisp; for commit privileges submit a pull request.
-
nixery
Container registry which transparently builds images using the Nix package manager. Canonical repository is https://cs.tvl.fyi/depot/-/tree/tools/nixery
-
-
-
-
-
-
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
niv discussion
niv reviews and mentions
-
NixOS. Managing secrets with sops-nix
For use on a local machine. We will use niv to install sops-nix.
-
Using niv to Manage Haskell Dependencies
Sometimes, nixpkgs does not have the Haskell package version I need. In this case, I override the package with a custom one in the Haskell package set. I use niv to pin the version of the package I want to use. If I want to add it from GitHub, that is easy:
-
NixOS + Haskell best practices circa March 2023
niv
-
Pulling themes from a git project: the nix way?
Flakes work. An alternative is niv which was once popular and provides a good developer experience.
-
What are the biggest Pain Points with NIX? And what makes it worth the pain?
Essentially you can just think of it as a standardized default.nix/shell.nix with built-in Niv integration.
-
Our Roadmap for Nix
I agree that the FP part is not the only issue. It's that the community feels a bit more academic/I'll fix this for myself in the way that works best for me.
You can indeed achieve some reproducibility with Docker. It's tricky though, as you'd have to pin exact package versions of software. If you'd `FROM ubuntu:$VERION`, and would run an `apt-get update`, you're not guaranteed to get the same software.
Nix is like ZFS, as that it breaks the wall between two previously distinct area's. Those being building software, and installing/configuration software on your OS. It's quite different from the snapshot-everything methodology that Docker uses. Yeah, one can split in multi-stage images etc, but than you'll be keeping track of which dependencies need to be moved between the stages yourself, in a manner that cannot be abstracted away, so you're doomed to repeat the same patterns over and over again.
People also state that LVM + ext3 is more than sufficient compared to the complexity of ZFS. They miss out on the fact on how much more fine grained solutions are possible with ZFS.
I've used niv [0] before flakes arrived, and am actually still using that instead of flakes. The experimental nature of them has scared me away from them, as I'm not daily involved in this ecosystem at the moment.
[0] https://github.com/nmattia/niv#niv
-
Simplest way to set up neovim
You can use something like Niv to manage additional sources. I use it to fetch some Emacs packages, for example ligature.el. Then you update the package using $ niv update.
-
Unstable vs Stable channels
One thing that made this easier was switching from using Nix channels to explicitly pinning my dependencies with Niv. I honestly never fully understood how channels worked, and it's just much nicer to have everything specified in my Git repo. The exact commit of Nixpkgs that I'm using is in my sources.json file, so "reverting" just means checking out an older commit of my configs from Git then running nixos-rebuild switch. If I were redoing my dotfiles today I'd probably use Nix Flakes rather than Niv, but I suspect that Niv is still an easier option to get started with.
-
Remove unused niv packages
Does someone know of a way to remove unused pinned packages via [niv](https://github.com/nmattia/niv)?
-
How to downgrade single package?
Pin nixpkgs, and version control it. If you're using flakes, then just version control the flake.lock alongside your configuration. If you're not using flakes, you can use niv to easily pin nipxkgs, at the expense of some boiler plate.
-
A note from our sponsor - InfluxDB
www.influxdata.com | 13 May 2025
Stats
nmattia/niv is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of niv is Haskell.