What's the current best-in-class approach to packaging Elixir/Erlang/BEAM applications using Nix+releases as of July 2020?

Hey all, I have currently the same opinion as @DianaOlympos.

Reproducing the complete behavior of mix & rebar as a package manager within Nix seems a bit of too much work from my point of view (the .lock file is fine).
Even if I see the benefits this approach would bring - super super fast rebuilds in CI.
But in my work habit the dependence list in the .lock file is still countable and changes to my .lock file aren’t happening daily.
So a rebuild of + half a minute more is total acceptable occasionally.

But I have to explain my main usage or Nix with Elixir is the setup process for having a reproducible development environment.
So I’m aware in other main usage scenarios different things could be more valuable.

@shanesveller if you haven’t found my sample repo for showing off how I’m using Nix with Elixir currently → github.com/cw789/elixir_nix_seed

My future “goal” (not active working on it) for Nix & Elixir is cross compilation.
To have an easy setup where I can build releases and deploy on different architectures already including ERTS.

1 Like