3 ms·
That's absolutely correct. There are a couple of other things about it that make it much more useful than that ssh command: - You don't need to have access to
by inconshreveable 13y ago
That's absolutely correct. There are a couple of other things about it that make it much more useful than that ssh command:
- You don't need to have access to a private server to use it.
- I've taken care of setting up SSL for you. So you can run your local server with just http but still have the entire public connection portion be encrypted.
- ngrok captures all of the http traffic over the tunnel, analyzes it and displays a local web interface for you to inspect the traffic.
- ngrok allows you to pick any request that happened over the tunnel and replay it to your local server. This is immensely useful for building webhook consumers.
- ngrok automatically reconnects if your internet connection is intermittent.
- It's written in Go so I can distribute it as a binary for all major platforms with zero dependenices.
I'll work on improving the copy. Thanks for the feedback!
- finnh 13y agoIt also took me awhile to figure out what ngrok does. Once I did, I can see the usefulness for sure. One path would be a list like you provide above, a sort of "your situation / your solution" approach, something like: You ... are developing a website/service your local machine You ... want to allow friends to test from outside your LAN BUT: You ... don't want to open a firewall hole to your DEV machine You ... want secure connections, but don't want to setup a valid cert You ... don't want to bother with your own reverse proxy AND You ... do want an inspectable, replayable copy of all traffic That's where we come in! obviously my text is clunky, but that sort of explanation would help me understand what "hassle" you are helping me avoid.