-
-
Notifications
You must be signed in to change notification settings - Fork 298
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
In the examples, listen on 0.0.0.0 instead of 127.0.0.1 #664
Comments
Nice catch. PR are welcome! |
Alright, I'll make a PR - just to be sure, I didn't mention it in the original issue, listening on 0.0.0.0 means that the developer will most likely expose their poem service on the local network (in the case where it's not running in a container). Just wanted to mention that. |
Yes, we may add some comments on |
Not sure if I've forgotten anything, but this should be everything in examples/ plus README's and a couple doc comments |
seems finished. Please reopen if anything is wrong. |
Listening from localhost (127.0.0.1) might work well for a development environment, but when deployed in a docker container the service will not be accessible from outside. Especially for people that know little about networking / docker in general, something like this can be very frustrating to debug - the container will be running, networking will be correctly setup, but every connection is refused.
The text was updated successfully, but these errors were encountered: