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 management between instances #9

Open
psihius opened this issue May 1, 2017 · 5 comments
Open

Port management between instances #9

psihius opened this issue May 1, 2017 · 5 comments

Comments

@psihius
Copy link
Member

psihius commented May 1, 2017

Well, I run into this myself with the latest event - I forgot to define specific ports for each server, and had to read the log to see that I derped.
I voiced an idea to put a file into the instance config folder like "port.xxxxx" and read those when creating a new instance, so we can assign a unique port to the instance.

@maikelwever
Copy link
Contributor

Would it also be okay to re-use the existing SERVER_PORT= parameter in init.conf?

@psihius
Copy link
Member Author

psihius commented May 1, 2017

Yes, reusing SERVER_PORT is best, just need to make sure it does not collide.
Extra level - reuse ports that were used by deleted instances :)

@maikelwever
Copy link
Contributor

Using a non-default port does not have any implication on the game: eg: the game can still be found in the server browser?

@zackman0010
Copy link

Correct, port does not affect the ability to be seen in the server browser

@psihius
Copy link
Member Author

psihius commented May 1, 2017

Ofcourse, the game is connecting to the server browser and telling it where it can find it, not the other way around. Otherwise you could not run multiple servers on a single IP address :)

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

3 participants