-
-
Notifications
You must be signed in to change notification settings - Fork 115
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
Add server IP Chooser #735
Conversation
@juuz0 Thank you, I will give a check. |
Updated for latest changes in kiwix/libkiwix#622 |
@juuz0 It does not compile for me:
|
It compiles now, but I have a dubious warning:
Otherwise looks pretty good:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks almost perfect, but needs a bit of beautiful.
@kelson42 I agree on the beauty, haha. Will do them changes |
Updated @kelson42 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Few things left:
- Default port should be
8080
99999
input should not be possible at port number. Only values from 1 through 65535 are authorized.
Both done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well done
@mgautierfr Can you please have a look to the code? |
ff3ca6a
to
123dc2d
Compare
@juuz0 I have rebased and hopefuly, now that kiwix/libkiwix#622 has been merged, the CI will pass. But I have remarked a small glitch: Why in the selectbox, we have an empty entry, or at least a white margin, at the bottom of the IP list? |
@kelson42 was an issue with padding, I removed the padding from there and decreased the Port Edit box's to 2px. |
@mgautierfr We really need to move ahead with this PR, please review it quickly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only values from 1 through 65535 are authorized.
I wonder if we should go even further and prevent port < 1024.
Those ports are "Well-known ports" and most of the time (on linux at least), the user needs to be root to use them. We probably don't want to use them. (See https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers)
@mgautierfr Not sure about that, port 80 is legit for example. I would avoid that discussion for the moment or at least pospone it in an other ticket. |
port 80 is legit for a "real" server. Something running as a daemon and probably with some monitoring (and on linux you need root access) |
Look good to me. @juuz0 Please rebase/fixup before we merge. |
Allow port settings to be changed from local server dialog
Use default port if there is no value
For better user experience
@juuz0 Thx, great to see this PR finally merged and working so well! |
Yay! :D |
Fixes #322
Fixes #726
Needs kiwix/libkiwix#622