relx

问题 I created a release using rebar3 but I have issues running/booting the app on my remote server. When i run the following command: $> /home/app/releases/0.0.1# erl -boot start I get the following error: {"init terminating in do_boot",'cannot expand $ERTS_LIB_DIR in bootfile'} init terminating in do_boot (cannot expand $ERTS_LIB_DIR in bootfile) Crash dump is being written to: erl_crash.dump...done What am I doing wrong? 回答1: How are you creating a release? If you do something like rebar3 as

问题 I try to use relx for release application. Relx did it without problems. But when I start application, I have the error: {"Kernel pid terminated",application_controller," {application_start_failure,iqServer,{bad_return,{{iqServer_app,start,[normal,[]]}, {'EXIT',{undef,[{iqServer_app,start,[normal,[]],[]}, {application_master,start_it_old,4,[{file,\"application_master.erl\"}, {line,272}]}]}}}}}"} As I understand from the error, I have a problem in the function iqServer:start/2 . start/2 looks

问题 I am building my release using relx and I can not use the default -sname someuser@127.0.0.1 . Instead I would like to do something like -sname someuser@`hostname -i` to define the node's public IP at boot time. Using -sname someuser@ hostname -i`` does not work because hostname -i is not expanded to a real IP. I tried to use net_kernel:start(xxxxxxx) but it did not work. Is there any way to get a dynamic -sname in vm.args using relx ? Thanks :) 回答1: As written in the documentation (and