-
Notifications
You must be signed in to change notification settings - Fork 9
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 a command line option for what interface to listen on #34
Conversation
I couldn't manage to reach happiness, but it might be due to either me setting up the program incorrectly, or my bug report having fundamentally misunderstood how containers work.
Indeed:
|
@badp that looks like an issue setting up the environment, indeed: there's an additional step to install pacparser (which has a build step) into the environment. If you prefer |
okay, that |
Starting over (I happened to have all of the required packages installed with apt anyway -- I did install the software!)
By the name of the parameter, "interface", I expected to be able to say "docker0" and have it work, but I don't suppose it's a huge deal breaker. Stack Overflow says you may be able to get the IP address for a given interface with this:
Of course, that [0] is pretty scary hardcoding, and (more importantly) that's an additional dependency for your project, and your packaging, PPA, etc., so I'm happy to take the patch as-is and kludge the IP address myself with some |
@badp heads-up: I just changed the name for this option to |
This may be useful for exposing pac4cli to containers (cf. #33). Choosing `-s` for the short form as that agrees with `netcat`.
The original reporter was confused, and this name is the same as what python's `http.server` module uses.
1df6991
to
992bcf7
Compare
This may be useful for exposing pac4cli to containers (cf. #33).
Choosing
-s
for the short form as that agrees withnetcat
.This is WIP, so let's not merge until we hear back from the issue author.