rebar3

How to get an Erlang app to run at starting rebar3

假如想象 提交于 2019-12-07 15:34:25
问题 I can start the application manually from the rebar3 shell by doing application:start(lager) followed by application:start(myapp) . I'd like this to happen without having to type it out, for example by executing a shell script that tells rebar3 to run those commands. Is this possible? 回答1: Assuming that you want to run the application during development you can do it like this: either you specify the apps at commandline like this: rebar3 shell --apps lager myapp or you specify in rebar.config

How to get an Erlang app to run at starting rebar3

 ̄綄美尐妖づ 提交于 2019-12-06 01:44:20
I can start the application manually from the rebar3 shell by doing application:start(lager) followed by application:start(myapp) . I'd like this to happen without having to type it out, for example by executing a shell script that tells rebar3 to run those commands. Is this possible? Assuming that you want to run the application during development you can do it like this: either you specify the apps at commandline like this: rebar3 shell --apps lager myapp or you specify in rebar.config {shell, [{apps, [lager, myapp]}]}. and then simply run it with rebar3 shell . For example I have an

Rebar3 + Cowboy Kernel PID Terminated

别说谁变了你拦得住时间么 提交于 2019-12-04 06:10:08
问题 I installed rebar3 and created a new release with cd ~/apps rebar3 new release tunnel Then I copied my src files from ~/tunnel/src/* to ~/apps/tunnel/src/ I ran into a compile error with rebar3 run and found Erlang "Kernel pid terminated" error as a possible solution. I renamed everything about tunnel_app to tunnel . So my src contains tunnel.erl , tunnel.app.src and tunnel_sup.erl . I renamed the module definition as appropriate. Here's the rebar3 run error: ~/apps/tunnel:.rebar3 run ===>