I definitely am, and it has already cleared up some confusion for me about how to handle config at build/run time, and releases in general. Really happy to see progress here.
I am SO EXCITED for these particular improvements! Releases and configuration (in general but more specifically for releases) have been really the only two pain points for me in my time using Elixir. I am so glad Jose and the others have decided to make these two points a priority.
I’m looking forward to blog posts and articles covering these new features
Basic release handling and the config changes are certainly a big deal. Also the docs for mix release are incredibly well written. I’m just a bit sad my contributions to EEx didn’t make the cut into the blogpost. It’ll allow the use of functions with more than one callback/do/end block allowing to build things like complex components with multiple “slots”.
I’ve been waiting for 1.9 to start looking seriously at releases. Right now I build a docker container with MIX_ENV=prod as part of the build process, then I just mix run in production.
One of the things I’m wondering is what about when I want to use mix in production, e.g. to run migrations, or to import a seeds file. My understanding is that mix isn’t available inside a release.
I haven’t seen any examples of running migrations with the 1.9 releases, but I imagine it would be similar to distillery https://hexdocs.pm/distillery/guides/running_migrations.html. While distillery has some conveniences for this, I haven’t seen anything for 1.9 releases.
But basically setting up the code or a script that runs the same code that the command mix ecto.migrate does (look at the example code I linked).