For practical purposes, I packaged the whole application as a single escript archive.
This resulted in a rather annoying problem: while the master node has no problem loading modules from this escript archive, the peer nodes do.
I've tried adding the "inside of the archive" to their load path when starting them, similar to how the master node has it on its own load path, but its not possible.
I had to unzip the archive and dump the modules required by the peer nodes to their load paths.
My theory is that the runtime hides the fact that its an archive, and does the same unzipping and loading in the background, so you don't have to do this on the main node.
It would be nice to investigate this further and avoid this hack.
For practical purposes, I packaged the whole application as a single escript archive.
This resulted in a rather annoying problem: while the master node has no problem loading modules from this escript archive, the peer nodes do.
I've tried adding the "inside of the archive" to their load path when starting them, similar to how the master node has it on its own load path, but its not possible.
I had to unzip the archive and dump the modules required by the peer nodes to their load paths.
My theory is that the runtime hides the fact that its an archive, and does the same unzipping and loading in the background, so you don't have to do this on the main node.
It would be nice to investigate this further and avoid this hack.