<html><head></head><body>In my project we're isolated from the internet when building, something which the elixir package manager doesn't like very much, which mix defaults to using.<br><br>We ended up downloading a version of hex into a folder and also a binary version of rebar3 for building our Erlang dependencies, the configured or build system to use those.<br><br>Mix can build a full deployable release including an ERTS if needed, both from elixir and Erlang sources. So I know it can definitely be done. The only somewhat annoying thing is that the setup always starts rebar3 for compiling dependencies even if nothing is to be done. But after being started rebar3 at least recognizes nothing needs rebuilding.<br><br>If such a setup is interesting for you I could provide you with some details. It requires installing elixir for the build tooling but you can still do all your coding in Erlang as you wish.<br><br>Oliver<br><br><div class="gmail_quote">On 3 February 2022 21:03:42 CET, Joseph Lloyd <josarlo84@gmail.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div dir="ltr">I need a way of building Erlang apps and releases on an internal corporate network that is intentionally isolated from the internet. I have tried installing rebar3 without success so far. Has anyone done this? Are there better ways of achieving offline builds of erlang apps/releases?<div><br></div><div>Thanks,</div><div><br></div><div>Joseph</div></div>
</blockquote></div><div style='white-space: pre-wrap'><div class='k9mail-signature'>-- <br>Sent from my Android device with K-9 Mail. Please excuse my brevity.</div></div></body></html>