stefanchrobot
How to prevent a node becoming distributed if started by a release?
Once my application starts, I want to talk to Consul to figure out other running nodes and connect them into a cluster. I want to customize my node’s longname and cookie.
The problem seems to be that the node is automatically started as a distributed node since I’m using releases. Therefore I can’t use :net_kernel.start (already started) nor :net_kernel.stop (not allowed).
Is there a way to do it? Or do I need to put all the logic into the env.sh?
Most Liked
josevalim
I think setting start_distribution to false won’t allow you to start it properly later. If you do try to allow it, the system will be in a borked state with missing components.
This feature is not supported by Elixir releases, so please open up an issue. We should add support for something like RELEASE_DISTRIBUTION=noname.
Last Post!
stefanchrobot
Popular in Questions
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #elixirconf-us
- #advent-of-code
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #hex
- #security









