Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

port conflict strategy #56

Open
davidmarkclements opened this issue Oct 23, 2015 · 1 comment
Open

port conflict strategy #56

davidmarkclements opened this issue Oct 23, 2015 · 1 comment

Comments

@davidmarkclements
Copy link

currently deck uses port 2000 9999 35729 and if in tunnel mode also 9998 and 35278. to avoid port conflicts, we need to use something like the find-port module to dynamically assign to a port for each cases (these cases are not dispersed throughout the system) - we then need every aspect of the system to read from a port config instead of the hard coded values

@davidmarkclements
Copy link
Author

doing this also allows for multiple instances of deck

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant