Instructions for running on port 80 #70
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
On Debian at least (haven't tested on other servers) I was unable to listen on port 80. Most people expect that the webserver will listen on port 80 and typing in any other port number explicitly is less than ideal. I've added a work around that forwards port 80 to 3000 (default) and this works for me.
|
I appreciate the change, but I think this is too specific for our little README. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On Debian at least (haven't tested on other servers) I was unable to listen on port 80. Most people expect that the webserver will listen on port 80 and typing in any other port number explicitly is less than ideal. I've added a work around that forwards port 80 to 3000 (default) and this works for me.