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

Fix gunicorn deployment to listen on preferred network #65

Open
jfischer opened this issue May 3, 2012 · 0 comments
Open

Fix gunicorn deployment to listen on preferred network #65

jfischer opened this issue May 3, 2012 · 0 comments
Assignees

Comments

@jfischer
Copy link
Contributor

jfischer commented May 3, 2012

To get things working, the new gunicorn fileserver listens on 0.0.0.0. We prefer to have it only listen on the ip address that will be given to clients. Need to think about the best way to do this. We might use the private ip if provided in the host resource. In that case, we probably should use the same logic as djm - add public ip, hostname, and private ip to the definition and use priority order to select a default.

Also need to think about how to coordinate the url generation in the code with the listen address. One option is just to write out the bind address to a well-known file.

@ghost ghost assigned jfischer May 3, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant