Elixir Blog Posts

[hubertlepicki]

I have blogged about configuration & Elixir here:

Elixir: Runtime vs. compile time configuration

that builds upon some discussions we’ve been having here, most notably:

What is the difference between using {:system, "PORT"} and System.get_env("PORT") in deployment?

I want to update this old discussion and thread to say we have come up with a mechanism that no longer requires {:system, ...} and it is slowly being deprecated from Phoenix, Plug and Ecto. James Fish pointed out the best place to do configuration is inside init/1. Doing it before calling start_link is an issue because then it won’t work with hot code reloading. Therefore with Phoenix v1.3, we are going to push dynamic configuration, such as the ones loaded from the environment, to the init fun…

Proposal: moving towards discoverable config files

One of the major differences between running your application as a release and as a Mix project is the differences in configuration. Mix evaluates the configuration right before the application starts, releases evaluates the configuration when your application is compiled. This implies in a large mismatch of how those two environments are used. For releases, environment variables (read by System.get_env/1) need to be set when the application is compiled and such information may not be available…

Distillery 2.0 has been released

Here’s a quick overview of the major changes: A solution to the problem of runtime configuration Improved experience around hot upgrades/downgrades, namely better support for custom appups and programmatically modifying them Out of the box support for generating PID files Better and more consistent primitives for custom commands and hooks Improved errors and better feedback from the CLI Major improvements to the documentation: new guides, better organization, searchable docs, and more