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

Dockerfile: Specifies comments on exposed ports #5615

Merged
merged 2 commits into from
Oct 23, 2018
Merged

Dockerfile: Specifies comments on exposed ports #5615

merged 2 commits into from
Oct 23, 2018

Conversation

funkyfuture
Copy link
Contributor

this pr addresses #5610. i have no clue what websocket transfer is in this context, that part may be very wrong.

Stebalien
Stebalien previously approved these changes Oct 22, 2018
Copy link
Member

@Stebalien Stebalien left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One thing but looks good otherwise.

Dockerfile Outdated
EXPOSE 8080
# Swarm Websockets; must be exposed publilcy when websocket transfer is enabled
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the websocket transport. That is, you can listen on /ip4/0.0.0.0/tcp/8081/ws to accept connections from peers (usually browsers) using the websocket libp2p transport.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could you provide a proposal for the wording? (there's that new cool feature here on gh.) i don't fully get what your response means regarding my proposal.

@Stebalien Stebalien dismissed their stale review October 23, 2018 00:00

s/transfer/transport

Dockerfile Outdated Show resolved Hide resolved
@Stebalien Stebalien merged commit dcecab6 into ipfs:master Oct 23, 2018
@funkyfuture funkyfuture deleted the patch-1 branch October 23, 2018 19:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants