Nix? Yes, I can write something about it. It is not that hard to be honest, especially in simple cases.
hauleth
cnck1387
Would you classify Docker as none or other?
I’m thinking other, since technically it’s a way to version control your projects.
It’s what I use for everything.
3
dimitarvp
Really tired of hearing “it’s not that hard”. 
We all have different skill sets even if we have one profession around here. So don’t think what comes easy to you is just as easy for others. The reverse examples surely exist as well.
So please, write blog posts. 
They will be much appreciated.
4
AstonJ
Thanks to everyone who voted and commented, especially about asdf… I too am now a convert 
I really like how simple everything was, well done @HashNuke, @vic, @Stratus3D and everyone who’s worked on it
(If anybody needs a guide on setting up a dev environment on macOS, here’s one I just put up.)
3
strzibny
Whenever I can I just grab a package from Fedora/CentOS repo. If the project needs different version I used exenv since have some experience with rbenv.
1
webuhu
I in person can’t serve with a blog post right now.
But you can have a look at my sample repo → Elixir Nix Seed.
And on any questions, just mail me.
2
Stratus3D
Asdf Core Team
Yes! asdf-erlang uses kerl underneath. Using it allows us to reuse a popular build tool that knows how properly configure Erlang for most popular OSes today. Kerl is an excellent tool and there isn’t anything we could have improved on. The only reasons asdf-erlang exists is to make kerl fit the asdf why of doing things.
4
Will-W
I’ve started using Nix recently. The main benefit to me is that your CI environment always matches your development environment, and does it without the overhead and faff of (e.g.) managing docker containers.
The bare minimum for Elixir would be a shell.nix file in the root that looks like this:
{ pkgs ? import <nixpkgs> {} }:
with pkgs;
let
inherit (lib) optional optionals;
elixir = beam.packages.erlangR22.elixir_1_9;
nodejs = nodejs-10_x;
in
mkShell {
buildInputs = [ elixir nodejs ]
++ optional stdenv.isLinux libnotify # For ExUnit Notifier on Linux.
++ optional stdenv.isLinux inotify-tools; # For file_system on Linux.
LOCALE_ARCHIVE = if pkgs.stdenv.isLinux then "${pkgs.glibcLocales}/lib/locale/locale-archive" else "";
}
Then you can run nix-shell to create a prompt with the tools in (I don’t use --pure much as I’m using git etc out of host package manager).
Then in CI, you can start with basic Nix docker image and run nix-env -f shell.nix -i -A buildInputs to get exactly the same environment. This is my full .gitlab-ci.yml file:
image: nixos/nix:latest
variables:
MIX_ENV: "test"
before_script:
- nix-env -f shell.nix -i -A buildInputs
- mix local.rebar --force
- mix local.hex --force
- mix deps.get --only test
mix:
script:
- mix test
3
halostatue
I use kiex and kerl with direnv. I’ve built a little bit of support tooling for direnv for all of this (and I use fish-nvm as I switched to fish).
My preferred Ruby version manager is chruby with ruby-build, although I’m trying to use direnv for a lot of this now.
0
