No way to set node name with mad

synrc / mad

⚡ MAD: Managing Application Dependencies LING/UNIX

https://mad.n2o.dev

Other

173 stars 53 forks source link

Open xafizoff opened 5 years ago

xafizoff commented 5 years ago

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 commented 5 years ago

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

$(mad start)

just like with $(mad attach).

xafizoff commented 5 years ago

Solved with

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

5HT commented 5 years ago

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

5HT commented 5 years ago

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

xafizoff commented 5 years ago

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

5HT commented 5 years ago

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 commented 5 years ago

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

5HT commented 5 years ago

it's not necessary

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