You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is no option to run more than one tunnel, nor in documentation nor in code. But there is mention that one should use --parallel in case of multiple binaries run
Expected Behavior
Either documentation should state how to achieve it( generally aka spawn multiple time in the loop or state how to pass a list of desired tunnels)
Actual Behavior
No available documentation on how to start more then one tunnel from the same host using module
There is no option to run more than one tunnel, nor in documentation nor in code. But there is mention that one should use --parallel in case of multiple binaries run
The text was updated successfully, but these errors were encountered:
The --parallel-runs flag is used to specify the number of parallel tests you are running. The binary will then spawn an appropriate number of forks for the binary. This does not start multiple tunnels.
In case you need to start multiple tunnels, you can use the local identifier option which should allow you to spawn multiple binaries. You will need to run multiple node processes with different local identifiers depending upon the number of tunnels you want to create.
There is no option to run more than one tunnel, nor in documentation nor in code. But there is mention that one should use --parallel in case of multiple binaries run
Expected Behavior
Either documentation should state how to achieve it( generally aka spawn multiple time in the loop or state how to pass a list of desired tunnels)
Actual Behavior
No available documentation on how to start more then one tunnel from the same host using module
Steps to Reproduce the Problem
1.Open https://github.com/browserstack/browserstack-local-nodejs and look through it.
browserstack local arguments
Platform details
Details
There is no option to run more than one tunnel, nor in documentation nor in code. But there is mention that one should use --parallel in case of multiple binaries run
The text was updated successfully, but these errors were encountered: