-
Notifications
You must be signed in to change notification settings - Fork 6
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
Document the purpose of each open port #61
Comments
Yes and no. In a proper setup there shouldn't be |
Sure, I'll add this to my to-do list; thanks for the suggestion. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is important for those who run this service along others (potential port conflicts). In particular, what needs to be known if any of these need to be actually exposed. Is the webapp required to listen on port 3000 outside the container, for example?
The text was updated successfully, but these errors were encountered: