Run ngrok on specified port #296
Open
Conversation
This file contains hidden or 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
|
This config will impact our Ubuntu Server Side Scripts as some deploys at port 80 and port 443 based on whether SSL is enabled or not. |
|
Oh, but then how can we allow the user to configure for a specific port? A new env var called NGROK_PORT? |
|
thats a best idea. let me think |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Currently, ngrok runs on port 80 by default. This change points ngrok to the port where the flask process is running. For example, I run OpenAlgo Flask process on 5001 port, but when I have ngrok tunnelling turned on, the ngrok process points to port 80.