All of my projects compile and test with no errors on 1.9. I haven’t tried releases yet. Is there a migration guide from distillery?
lukaszsamson
ElixirLS Core Team
blatyo
Conduit Core Team
jeremyjh
josevalim
Creator of Elixir
samuba
Once a release is assembled, it can be packaged and deployed to a target as long as the target runs on the same operating system (OS) distribution and version as the machine running the
mix releasecommand.
Are there plans to remove those limitations in the future?
0
OvermindDL1
I’ve never seen the BEAM have any sort of cross-compilation to date, in addition the NIF’s would have to be cross-compiled in whatever language they are written and so forth as well. I.E. it’s not possible in any easy timeframe.
2
alexdovzhanyn
garazdawi
Erlang Core Team
Quite a few products that I know of uses the cross compilation support to build Erlang/OTP.
However as you say, cross compiling nifs is a problem as many nifs writers have not done what needs to be done in order to make cross compilation work. I put together syslogger as an example/experiment of how one could achieve cross-compilation for nifs (if you ignore cross compiling to windows).
6
jswny
Can anyone comment on how much the new release process and configuration tools have improved in terms of deploying Phoenix?
A while ago I wrote up a guide for myself since the previous process was pretty complicated and it was the Distillery docs that were the only ones that even had the setup for Phoenix.
The pain points for me were:
- Having to go through the Distillery docs in order to deploy a Phoenix application (they were pretty good but lacking in some areas and had bugs in others). There was also a general lack of guidance on how to do more advanced things.
- Having to figure out how to use environment variables for configuration at runtime in a release or figure out how to properly set the configuration with environment variables when building a release.
- Having to create special code and special release tasks just to run migrations when those could already be run from the command line with mix. This included having to setup shell scripts.
- Figuring out how to load the secret key from an environment variable at runtime.
- Little to no information regarding Postgres/Ecto in general (the new version of the docs has almost no information at all).
1
josevalim
Creator of Elixir
Regarding documentation, those concerns aren’t solved right now (it is too soon) but I believe it will be solved in the short term as, by being part of core, more people will use it, battle test it, document it, write guides, etc. For example, [latest Ecto ships with functions(Add Ecto.Migrator.with_repo/2 to start/stop apps for migrations by josevalim · Pull Request #113 · elixir-ecto/ecto_sql · GitHub) that make running Ecto tasks inside a release very straightforward]. Phoenix guides will also be updated to cover it.
In particular:
Phoenix will ship with guides for this (it also does for distillery though).
There is a well-documented path for this in Elixir releases (TL;DR - there is a config/releases.exs that runs on release boot).
Custom code is still necessary for Elixir but you don’t need shell scripts. Only a module with functions you will invoke. See the Ecto link above and the official guides. The Hex migration (which is a Phoenix app) covered this too: Updating Hex.pm to use Elixir releases « Plataformatec Blog
Same as above other environments variables: just put it in config/releases.exs. In fact, for Phoenix v1.4 projects, getting it to work is a matter of renaming config/prod.secret.exs to config/releases.exs.
7