rfcs
asdf
Our great sponsors
rfcs | asdf | |
---|---|---|
46 | 339 | |
476 | 20,215 | |
6.3% | 3.0% | |
5.0 | 7.9 | |
3 days ago | 11 days ago | |
Shell | ||
Creative Commons Attribution Share Alike 4.0 | 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.
rfcs
-
Build System Schism: The Curse of Meta Build Systems
Nix with dynamic derivations (RFC92) could potentially beat this curse.
https://github.com/NixOS/rfcs/blob/master/rfcs/0092-plan-dyn...
-
Show HN: Flox 1.0 – Open-source dev env as code with Nix
See: A plan to stabilize the new CLI and Flakes incrementally https://github.com/NixOS/rfcs/pull/136
- RSS can be used to distribute all sorts of information
-
I like gentoo's package deprecation process
NixOS recently introduced "problem" infrastructure to deal with such problems more gracefully and explicitly:
https://github.com/NixOS/rfcs/blob/master/rfcs/0127-issues-w...
-
NixOS and Flakes Book: An unofficial book for beginners (free)
For some more context: Flawed as they are, Flakes solve a large number of problems Nix experiences without them. This is why I, and presumably many others, use them even in their current experimental state.
An RFC was recently accepted to commit to forming a plan towards stabilization of Flakes: https://github.com/NixOS/rfcs/pull/136
Personally, I don't believe there won't be any breaking changes, but I also believe that the stabilization of Flakes is still a ways away and hope that there will be a reasonable migration path.
- NixOS RFC 136 accepted: A plan to stabilize the new CLI and Flakes incrementally
-
Super Colliding Nix Stores: Nix Flakes for Millions of Developers
> Afterwards, Flakes itself and its CLI components can be stabilized. The final design of Flakes will also require another RFC.
That seems like Flakes are still quite a ways away.
[1] - https://github.com/NixOS/rfcs/pull/136
First, the non-Flakes CLI wll be stabilized, in phases.
-
Lanzaboote vs. bootspec-secureboot
Both require the Bootspec patches, only support systemd-boot, have recent activity, and include a Rust-based tool for signing images.
-
Using NixOS as a Hypervisor for a k3s Cluster in Homelab, can I define the VMs in Nix config?
I just found an RFC for similar that was unfortunately closed back in the day: https://github.com/NixOS/rfcs/pull/12
-
Nix journey part 1: My grand unified theory of Nix documentation · Tinkering
If you'd like to understand, reading through https://github.com/NixOS/rfcs/pull/49 is probably a good place to start.
asdf
-
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
-
Pyenv – lets you easily switch between multiple versions of Python
https://asdf-vm.com/ ASDF is better because it works with many more languages, other than only Python, like Rust, Go, Node, etc, and other tools, such as AWS/Google/Firebase/Azure CLIs.
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).
-
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
git clone https://github.com/asdf-vm/asdf.git ~/.asdf --branch v0.13.1
-
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.
-
How do i keep my "devops tool" always up to date in a smart way ?
I use the asdf version manager.
What are some alternatives?
SDKMan - The SDKMAN! Command Line Interface
pyenv - Simple Python version management
rbenv - Manage your app's Ruby environment
nvm - Node Version Manager - POSIX-compliant bash script to manage multiple active node.js versions
volta - Volta: JS Toolchains as Code. ⚡
HomeBrew - 🍺 The missing package manager for macOS (or Linux)
mise - dev tools, env vars, task runner
jenv - Manage your Java environment
nvm for Windows - A node.js version management utility for Windows. Ironically written in Go.
fnm - 🚀 Fast and simple Node.js version manager, built in Rust
RVM - Ruby enVironment Manager (RVM)
nix - Nix, the purely functional package manager