No way to set node name with mad

[xafizoff]

AFAIK, it is not possible to start node with the given name. Even if I set

-name mynode@127.0.0.1

in vm.args, I get nonode@nohost

[xafizoff]

Actually, mad can just "generate" start script, so we can start with command

$(mad start)

just like with $(mad attach).

[xafizoff]

Solved with

$ mad bun beam myapp && tar -xzf myapp.tgz && chmod +x bin/start &&  && bin/start

[5HT]

No no, this is not a solution, you're right mad should do the chmod.

[5HT]

And mad start and mad releases are totally different things! Don't mix them in Issues.

[xafizoff]

The issue was not about start or release, it was about node name...

[5HT]

Yeah, but setting name in OTP release is known and trivial task by using vm.args.
While MAD release (escriptized) is a bit complicated.

[xafizoff]

I didn't know about beam-release... Anyways in dev-env it's not necessary.

[5HT]

it's not necessary

it could be. when you debug distributed setup (database e.g). Let this issue be open for now.