[erlang-questions] Include ERTS in an escript package
Fri Jan 11 08:40:54 CET 2019
As far I know, It is not possible to package runtime to escript with rebar3.
Easies, faster and reliable solution to package escript along with ERTS to docker...
Another options to package entire application and its deps to escript with rebar3, like you are doing it now.
Then prepare tarball with ERTS. You can either use of-the-shelf kerl builds, use Erlang Solution packages  or make a lightweight release that will weight 20 - 30MB. And ship both deliverables. If you’d like to ship a single file then you can make a self extracting tarball. I’ve shared a link to my project where I did similar . However, I’ve stopped doing it now and switched 100% to dockers.
> On 10 Jan 2019, at 23.48, Mark Geib <mark.geib.44@REDACTED> wrote:
> I normally build erlang releases with rebar3 for deployment in our production environments. I do not require erlang to be installed on these systems since the release includes erlang, etc.
> I have a need to provide a escript for some metrics gathering and housekeeping operations, but with no erlang on these production
> servers I am wondering what the best approach is to provide these escripts for production.
> My question, is it possible, with rebar3 to package an escript in such a way as to include erlang, eliminating the dependency of
> install erlang on these servers. This would also allow me to continue providing releases based on different versions of erlang that run
> on the same production server.
> erlang-questions mailing list
More information about the erlang-questions