I am writing my first erlang application and I want to do things the way they should be done in the erlang ecosystem. My app depends on ssl, inets services and log4erl application to be already started and as for now I start them manually in the erlang shell. After that I start my app's supervisor that starts other parts. The question is how should I organize things so that there would be no need to start ssl, inets and log4erl manually ?
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试):
问题:
回答1:
You should try Erlang release handling system.
Check docs here.
回答2:
Also see answers to this question for the explanation and some pointers to tools that make creating the releases easier. Extract below:
There are a few third-party tools that make creating releases easier, like rebar, relx, mad, erlang.mk, or builderl (no documentation for the last one yet, some example usages in those applications: humbundee, builderl_sample_project_sc).