niv
asdf
niv | asdf | |
---|---|---|
16 | 341 | |
1,462 | 20,547 | |
- | 1.6% | |
6.3 | 7.6 | |
about 2 months ago | 5 days ago | |
Haskell | Shell | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
niv
-
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.
- Compiling emacs is killing me
-
Ditch Your Version Manager
This... This is laughable. How do I install ruby 2.6.8? Oh, there's no ruby_2_6_8, because of course there isn't. And this could be difference between a secure system and all your base are belong to us.
And they call this reproducible builds?
And that's before getting into the ridiculous
--- start quote ---
All the software that we installed depends on the specific version of the nixpkgs channel that we installed on our system [whose only version is a commit hash in a git repo]
--- end quote ---
So you need an extra tool [2] for, quote, "painless dependencies for Nix projects."
Yes, sure. I'm definitely ditching my version managers in favor of this tool, that hasn't solved these issues in 18 years of its existence.
[1] https://search.nixos.org/packages?channel=21.05&from=0&size=...
[2] https://github.com/nmattia/niv
asdf
-
Install Asdf: One Runtime Manager to Rule All Dev Environments
The main issue most people have with asdf is that it’s annoyingly slow. Not unusably so, but just enough that it’s irritating.
I identified [0] the source for much of it (sub-shells and pipes) and began a PR [1], but became bogged down with BATS testing, and then found mise / rtx, so kind of lost interest. Sorry. You can always implement these if you’d like.
[0]: https://github.com/asdf-vm/asdf/issues/290#issuecomment-1383...
[1]: https://github.com/asdf-vm/asdf/pull/1441
- Show HN: I made a multiple runtime version manager that can be used on Windows
-
Volta – Fastest Node version manager in Rust
Or if you need to manage more than just node, asdf has been around for over a decade and works great. You can use a .tool-versions to change runtimes for each project you have, in addition to managing your global runtime versions
https://asdf-vm.com/
-
Pyenv – lets you easily switch between multiple versions of Python
Why not just use a tool like asdf (https://asdf-vm.com/) or mise (https://mise.jdx.dev/)?
These tools have the advantage of not being multi-taskers and can manage version for all your tools. You wouldn’t need pyenv and npm and rvm and…
We’ve even started committing the .mise.toml files for projects to our repos. That way, since we work on multiple projects that may need multiple versions of the same tool, it’s handled and documented.
-
A Journey to Find an Ultimate Development Environment
The purpose of a version manager is to help you navigate or install any tools for development easily. Version Manager can be one tool for each dependency (e.g. NVM, g) or One tool for all dependencies (e.g. asdf, mise).
-
How to Install Your Python Version on Ubuntu
(asdf)[https://asdf-vm.com/] fully supports Python and almost any other language. I've been using it for Ruby, Python, Elixir, and other languages for years and never looked back.
-
Beginners Intro to Trunk Based Development
Secondly, our development environments must not drift, because then code may behave differently and a change could pass on our machine but fail in production. There are many tools for locking down environments, e.g nix, pkgx, asdf, containers, etc., and they all share the common goal of being able to lock down dependencies for an environment accurately and deterministically. And that needs to be enforced in our local workflow so we don't have to rely on CI environments for correctness. All developers must have environments that are effectively identical to what runs in CI (which itself should be representative of the production environment).
-
Practical Guide to Trunk Based Development
There are many ways this can be done (e.g nix, pkgx, asdf, containers, etc.), and we won’t get into which specific tools to use, because we'll instead cover the essential essence of preventing environment drift:
- Criando seu ambiente com ASDF
-
Kotlin version manager
I've really been enjoying asdf, which is a program that allows you to install specified versions of dev utilities as well as dynamically manage them via shims and .tool-versions files.
What are some alternatives?
leksah - Haskell IDE
SDKMan - The SDKMAN! Command Line Interface
update-nix-fetchgit - A program to automatically update fetchgit values in Nix expressions
pyenv - Simple Python version management
ghcid - Very low feature GHCi based IDE
rbenv - Manage your app's Ruby environment
elm-make
nvm - Node Version Manager - POSIX-compliant bash script to manage multiple active node.js versions
hpc-threshold - Small utility for validating whether HPC result is above defined thresholds
volta - Volta: JS Toolchains as Code. ⚡
ihaskell - A Haskell kernel for the Jupyter project.
HomeBrew - 🍺 The missing package manager for macOS (or Linux)