AndyL

AndyL

Elixir 1.9 Release vs Distillery

It looks like Elixir 1.9 Releases are a subset of Distillery. (Is that right?)

When should someone use Elixir 1.9 Releases vs Distillery?

Are the two approaches mutually exclusive? Are there situations where you would want to use both toolsets?

First 2 of 2 Posts Switch mode

LostKobrakai

LostKobrakai

Elixir releases are a subset of distillery that’s correct. Currently there’s a bunch of overlap in functionality, as distillery basically had/has to do all the stuff elixir releases do. Especially as it’s still used for elixir <1.9 projects. Distillery also does more than elixir core releases. Most notably is the support for hot code updates in distillery.

As for when to use which: If you’re on elixir 1.9 (possibly without distillery already) I’d use core releases unless you need features only distillery provides. I’ve also heard people in slack note that elixir releases seem smaller than distillery ones, but I cannot confirm that, but might be worth looking into if file size is a concern.

I’d not try to mix them, as they are similar, but also very different: e.g. the cli in bin/ is completely different. Instead of changing distillery though I’d rather hope that distillery’s functionality will over time be extracted in (possibly smaller, more purpose build) new libraries, which hook into core releases using the :steps configuration available. I’m not sure how well this is possible for e.g. hot updates, but I’d expect adding things like build hooks or custom cli commands should be possible this way.

hubertlepicki

hubertlepicki

You want one or another, I think. I was sort of forced to switch to 1.9 releases because stumbled upon bugs with distillery + erlang + elixir in most recent versons. Which is a recurring pattern, and something to expect from external library.

Elixir releases are now internal part of Elixir, which means the chances are they won’t break as much on updating as distillery did. There’s absolutely no blame on distillery side, it’s just that carrying about multiple Elixir versions is obviously more difficult than carrying about one single current Elixir version. So the code base is in several places overcomplicated / bug prone because of that requirement, I suppose.

I was pleasantly surprised with the migration. I am very happy with how runtime config is handled. I kind of miss deploy hooks not being there but easy to work around, and probably for the best.

So in the long run, I think Elixir releases are the way to go for pretty much everyone. I suspect there’ll be a way to extend them with tools built on top of them, rather than distillery soon, so if you need some of the missing functionality you’ll be able to add it this way.

16
Post #2
— All posts loaded —

Where Next?

Trending in Questions Top

jonnycharles
I’m in search of an Elixir library that offers PDF generation capabilities similar to Ruby’s Prawn. While there have been discussions abo...
New
spammy
I’m looking to build a personal workflow to quickly deploy web applications written in elixir/phoenix, for local consumption (ie not on t...
New
silverdr
Using Phoenix.LiveView.TagEngine as an EEx.Engine is deprecated! To compile HEEx, use Phoenix.LiveView.TagEngine.compile/2 instead. Sta...
New
dli
Before I dive in myself, did anyone successfully sprinkle Hologram into their existing LiveView app? Looking for hints regarding: Addi...
New
bottlenecked
Hi all, I wanted to ask how the community is dealing with post-release steps. Today we have Ecto migrations, which make sure that the db...
New
michallepicki
I am using Oban and occasionally, shortly after a deployment, a handful of jobs can fail because of dependency on other parts of the syst...
New
rahultumpala
Hello, I have an Elixir backend that implements a custom protocol over TCP. I want to load test the backend and assess the performance o...
New

Other Trending Topics Top

JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Damirados
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge &amp; Solve. They are GUI (Emerge) and State management (S...
New
ausimian
Emily is an Elixir library that runs Nx computations on Apple’s MLX. Install it as the default Nx backend and Nx, defn, Axon, Nx.Serving,...
New
type1fool
I just stumbled on a newly redesigned elixir-lang.org. :tada: It looks like @Software_Mansion did the work, and I think it is generally a...
New
akoutmos
@hugobarauna and I (Alex Koutmos) have been hard at work on writing a book on Nerves that takes you from simply blinking LEDs to building...
New

We're in Beta

About us Mission Statement