a default node name is jellyfish@(hostname) - thanks to this, when using DNS strategy in docker we don't have to set JF_DIST_NODE_NAME explicitly
if hostname in node name in DNS strategy is not an ip address, we will try to resolve it under the hood
JF_DIST_MODE is snam by default - that's because of default node name
when JF_DIST_ENABLED is set, we always start the node in Elixir code. This means that if we make a release and we want to connect to already running node, we have to use RELEASE env vars i.e.
RELEASE_NODE=<JF_DIST_NODE_NAME(resolved in case of DNS)> RELEASE_COOKIE= RELEASE_DISTRIBUTION= _build/../jellyfish remote
To be precise, not always all of the above ones but this is quite tricky to describe
[x] I hereby confirm that a Pull Request involving updates to the Software Development Kit (SDK) has been smoothly merged, currently awaits processing, or is otherwise deemed unnecessary in this context.
[x] I also affirm that another Pull Request, specifically addressing updates to the documentation body (commonly referred to as 'docs'), has either been successfully incorporated, is in the process of review, or is considered superfluous under the prevailing circumstances.
After this PR:
jellyfish@(hostname)
- thanks to this, when using DNS strategy in docker we don't have to set JF_DIST_NODE_NAME explicitlyRELEASE_NODE=<JF_DIST_NODE_NAME(resolved in case of DNS)> RELEASE_COOKIE= RELEASE_DISTRIBUTION= _build/../jellyfish remote
To be precise, not always all of the above ones but this is quite tricky to describe
Documentation update jellyfish-dev/jellyfish-docs#72
Acknowledging the stipulations set forth: