-
-
Notifications
You must be signed in to change notification settings - Fork 114
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
Using IP address extracted from net interface #182
Comments
The proper syntax for all ip addresses is: It would be confusing to have: because eth0 is expected to be a hostname such as: I can't really think on a good syntax for this, does uWSGI supports this? |
Hello! I mean that we can add optional parameters: |
Ok, I had an idea, option Which will resolve the interface addresses and append them to the http-socket list, can you do a PR for this? |
I have no time at the moment (though I have done some primary dirty stuff in local copy). Should I consider only IPv4? Perhaps, I'll try to make a PR in mid-April. |
Well both IPv4 and IPv6 should be supported |
BTW, could you please explain parsing address & port in |
it's [IP]:PORT,ssl-cofig-files same syntax of uWSGI. |
Hello! If I use the following snippet (in ini file)
will REST server listen on all net interfaces?
Is it possible in future to put net interface name instead of hardcoded IP address?
For example,
It will be transformed programmatically into http-socket=192.168.21.50:3000.
I use the following heuristics (for IPv4) in other project (works for Linux (like
eth0
) and human-readable net interface names in Windows):The text was updated successfully, but these errors were encountered: