Update sockets.js - fixes CONFIG_FILE commands #6
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.
This makes sure that uses the commands in the config file given through CONFIG_FILE environment variable, it was using the custom ports and ips, as they are assigned first they do not change because of the socket being initiated, but the commands as they can be overwritten, was using the default config.json inside the xterm-express. I'm using this package to build simple monitors on request, maybe i'll share some usages xD!, thanks btw for this package, really helpfull!!!