Building Erlang Projects Offline
A. G. Madi
Thu Feb 3 21:33:29 CET 2022
I'm in the same position but I use rebar3. What I do is to download all
dependencies and move them to the internal network. I place them in the
_checkouts directory in my release's directory. That way rebar3 will find
everything it needs is already present and doesn't try to connect anywhere.
On Thu, Feb 3, 2022 at 14:27 Michael Truog <mjtruog@REDACTED> wrote:
> Hi Joseph,
> One approach is to use rebar2 for the build and reltool (included with
> Erlang/OTP) for the release. That approach is used in the
> https://github.com/CloudI/CloudI repository if you need an example.
> Best Regards,
> On 2/3/22 12:03 PM, Joseph Lloyd wrote:
> > 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?
> > Thanks,
> > Joseph
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions