Skip to content

Commit ebf2ebd

Browse files
Update README.md
1 parent 508ce5d commit ebf2ebd

File tree

1 file changed

+19
-2
lines changed

1 file changed

+19
-2
lines changed

README.md

Lines changed: 19 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,19 @@
1-
# teleport
2-
like ngrok but reverse
1+
# teleport - like ngrok but reverse
2+
3+
[ngrok](https://ngrok.io) is awesome. For those not in the know, ngrok addresses a use case where you want to expose a local server behind a NAT or firewall to the internet. Say you want to show your work to a colleague not on the local network - just run `ngrok http 3000` (assuming you're running your local server on port 3000) and you're given an HTTP address on the Wild Wild Web that you can share with your colleagues.
4+
5+
Except things sometimes won't work this way - sometimes things in your project only really work when run on localhost. This is the problem [teleport](https://github.com/codequest-eu/teleport) wants to address. It creates a TCP tunnel to a remote endpoint and passes connections from a selected port on the localhost (3000 by default) to the remote endpoint. This is a perfect companion for ngrok.
6+
7+
_Developer A_ wants to show her work:
8+
```bash
9+
$ ngrok tcp 3000 # gets an address like 0.tcp.ngrok.io:42644
10+
```
11+
12+
_Developer B_ wants to look at _A's_ work from the cosy confines of his localhost:
13+
```bash
14+
$ teleport -r 0.tcp.ngrok.io:42644
15+
```
16+
17+
Now for as long as this is running _Developer B_ can access localhost:3000 locally and connect via a magic gateway to _Developer A's_ server. Note that teleport works on TCP level so you will need to expose a TCP port with ngrok.
18+
19+
Of course nothing requires you to use teleport _only_ with ngrok - teleport will work standalone just fine so you can connect to a server running on your VPS as long as you can access it from your local machine.

0 commit comments

Comments
 (0)