Skip to content

Commit 54c07c5

Browse files
committed
added ngrok instructions
1 parent 3faccc2 commit 54c07c5

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

README.md

+2-1
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,7 @@ That is where RTConnect comes in - we take care of signaling and implementing We
1616
- [RTConnect Demo](#demo)
1717
- [Installation](#install)
1818
- [Getting Started with RTConnect](#implementation)
19+
- [Setting Up Public Endpoint/URL](#setting)
1920
- [Solutions/Fixes for Polyfill Errors](#errors)
2021
- [Contributing to RTConnect](#contribution)
2122
- [License](#license)
@@ -112,7 +113,7 @@ const App = () => {
112113
export default App;
113114
```
114115

115-
## Setting Up Public Endpoint/URL Using a Secure Tunnel Service
116+
## <a name="setting"/> Setting Up Public Endpoint/URL Using a Secure Tunnel Service
116117
In order to create a publicly accessible URL that will allow you to share access to your localhost server, you have a number of different options but a simple option is to use a secure tunnel service. One such free, secure tunnel service that you can use to create a secure, encrypted, publicly accessible endpoint/URL that other users can access over the Internet is ngrok.
117118

118119
ngrok Secure Tunnels operate by using a locally installed ngrok agent to establish a private connection to the ngrok service. Your localhost development server is mapped to an ngrok.io sub-domain, which a remote user can then access. Once the connection is established, you get a public endpoint that you or others can use to access your local port. When a user hits the public ngrok endpoint, the ngrok edge figures out where to route the request and forwards the request over an encrypted connection to the locally running ngrok agent.

0 commit comments

Comments
 (0)