distillery

+1 for distillery, very convenient... https://github.com/bitwalker/distillery

OTP releases let you build something akin to this, where the runtime and all the dependencies are bundled in; so long as you built it for the right architecture (much like a binary), it's a single command to run your app. This used to be done with Distillery[1], but I suspect its use will go down now that Elixir has native OTP releases.[2]. In either case, there's still work behind it, but it's not like deploying Ruby, Python, or Node, where you have to be pretty careful about library paths and runtime versions. [1]: https://github.com/bitwalker/distillery [2]: https://elixir-lang.org/blog/2019/06/24/elixir-v1-9-0-released/

> but you seem to have a non-factually supported negative bias against Elixir. If deployments are broken for months[1] with no fix in sight, what do you expect? I'm currently seeing zero requests per second with Elixr. If the sole maintainer of the sole deployment tool is too disengaged to reply to bug reports I don't care one way or another what sort of performance a product (or its fanbase) are claiming. If the product can't be deployed it's not going to scale. Period. It's a bit silly to talk performance comparisons between Ruby and Elixr as the premise of this article was that Ruby is simply too slow. Are you going to have a harder time scaling Go or Rust than Elixr? I doubt it. I have no idea if you're going to have a harder time scaling Java than Erlang, but Java is popular enough in the enterprise space that finding people w

The only reason I say that is that every project doesn't need hot-reloading. It's one of those things that is only recommended where you need it. Just think of it in the same way that you don't need every available jar file for a Java project. The capabilities of the system are expansive, but not always called for. Distillery is the main deployment related library out there for Elixir and reduces hot reloads to a an argument on the build. https://github.com/bitwalker/distillery/blob/master/docs/Wal...

Elixir and Erlang deployments were tricky a few years ago, but I feel like now with distillery [0] it a lot better. I use it in docker multistage builds [1] and have been really happy with that. [0] https://github.com/bitwalker/distillery [1] example dockerfile: https://gist.github.com/bsedat/16cb74ebc8ab0ed61ac598a129b0a...

A non-autoscaling deployment is quite easy to accomplish. Build releases with Distillery[1], and deploy them with Edeliver[2]. You get zero-downtime upgrades and rollbacks for free, as well as nearly automatic server clustering. I gave a talk about this last year in New York[3]. A deployment that can autoscale is harder to accomplish, but still not impossible. AFAICT, most people doing this are building releases with Distillery, wrapping those releases in a Docker image, then using the deployment and orchestration tools of their choice. Monica Hirst gave a talk about doing this with AWS CodeDeploy last year at Empire City Elixir as well[4]. [1] https://github.com/bitwalker/distillery [2] https://github.com/boldpoker/edeliver [3] https://www.youtube.com/watch?v=H686MDn4Lo8 [4] https://www.youtube.com/watch?v=mRspOj_sRgo

Distillery is highly recommended https://github.com/bitwalker/distillery

Deploying Elixir is extremely easy with Distillery, I think. https://github.com/bitwalker/distillery