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

BindAddress option #2477

Closed
grifball opened this issue Dec 1, 2016 · 2 comments · Fixed by karronoli/redpen#10
Closed

BindAddress option #2477

grifball opened this issue Dec 1, 2016 · 2 comments · Fixed by karronoli/redpen#10

Comments

@grifball
Copy link
Contributor

grifball commented Dec 1, 2016

I'm sorry if this option already exists and I just didn't notice it.
I'm using karma on a private project on a server with port 9876 open.
Rather than going through and closing that port in the firewall, it's easier just to bind to 127.0.0.1 instead of 0.0.0.0.
So I added support into karma for that, it's a simple change, I included a diff of the files.
I'm using karma version 1.3.0
diff new old.txt

Let me know what you guys think of having this option.

@maksimr
Copy link
Contributor

maksimr commented Dec 1, 2016

@grifball Karma don't have this option now
We had a pull request(PR) about it with long discussion.
It will be nice if you look at this PR and reanimate it

Thanks!

relates #1593

@grifball
Copy link
Contributor Author

grifball commented Dec 3, 2016

I looked at #1311 and #1214 and they both seem fine to solve this issue, so I added them in and fixed the unit tests so that the dummy web server accepts the correct arguments. I'll make a PR.

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

Successfully merging a pull request may close this issue.

2 participants