Update release.ex #8
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fix 'ExLoader.Release.get_path' on remote machine, not local - add param `remote_node` to function `get_paths ` - `File.ls!` should be `:rpc.call(remote_node, File, :ls!, [parent])` - `File.dir?` should be :rpc.call(remote_node, File, :dir?, [p])
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fix 'ExLoader.Release.get_path' on remote machine, not local
remote_nodeto functionget_pathsFile.ls!should be:rpc.call(remote_node, File, :ls!, [parent])File.dir?should be :rpc.call(remote_node, File, :dir?, [p]the test code
start_nodeisiex --sname #{name} --cookie #{:erlang.get_cookie()} --detached. it means nodes on the same machine, file system is the same too. but, when the remote node on remote machine, master and slave node in different file system. functionget_paths, should callFilemodule inrpcway.sorry for my poor English