3 ms·
> So you need environment managers: rvm, nvm, rbenv, pipenv, virtualenv, asdf, gvm… The list of acronyms just gets longer and longer. That's where Nix[1] shine
by ghostwriter 6y ago
> So you need environment managers: rvm, nvm, rbenv, pipenv, virtualenv, asdf, gvm… The list of acronyms just gets longer and longer.
That's where Nix[1] shines, as most of the times you no longer need these separate tools for creating individual isolated environments for specific languages/frameworks.
It also can help in partially replacing the local docker daemon for regular development tasks with images[2], with a help from Hocker[3]
[1] https://nix.dev/tutorials/ad-hoc-developer-environments.html https://nix.dev/tutorials/ad-hoc-developer-environments.html
[2] https://nix.dev/tutorials/building-and-running-docker-images.html https://nix.dev/tutorials/building-and-running-docker-images...
[3] https://awakesecurity.com/blog/hocker/ https://awakesecurity.com/blog/hocker/
- Shoue 6y agoI know it's mentioned in that tutorial under the next developer environment section but it's worth mentioning that direnv also makes it pretty much seamless because you can hook it into your shell of choice (I use Fish). It just drops the environment on you, that nix-shell would set up, the moment you step into that project's directory (after you've consented to it of course).
- aclatuts 6y agoasdf literally is designed to replace some of the stuff on that list and then some. And it negates the need for docker in some examples.