[erlang-questions] rebar3 dependencies

Tristan Sloughter <>
Sat Mar 19 01:32:47 CET 2016


> This use-case of rebar is an important one due to Erlang's focus on
> fault-tolerance.  To make sure your built is robust and stable,
it requires having all your dependencies at a known state.
 
Your build artifact for deployment is a release which does "bundle" all
dependencies at a certain point in time.
 
For reproducibility in the event of losing the original release is, as
you mention, what the lock files are for. When hex gains easy mirroring
there will also be a quick way to ensure you have your own backups of
alls your dependencies.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20160318/d169c470/attachment.html>


More information about the erlang-questions mailing list