Readit Newshi all, i'm the creator of ngrok. we released a similar SDK for Go a couple weeks ago [1] and we're really excited to make it just as easy to listen on the internet as it is to listen on a local port for all the Rustaceans out there now too :)
happy to answer any questions!
inconshreveable commented on ngrok-go: Ingress to Your Go Apps as a `net.Listener` blog.ngrok.com/posts/ngro... · Posted by u/dstotijn
hi all, i'm the author and creator of ngrok. we're really excited to make it just as easy to listen on the internet as it is to listen on a local port. happy to answer any questions
hi all, creator and founder of ngrok here!
we're super excited to share this release with the HN community. i'll try to answer any questions you have in the comments here.
we're making all of the functionality available for free until may so that you can try everything out. once you have an ngrok account visit https://dashboard.ngrok.com/launch-party to light up all the new features and give it a spin. we're eager to hear your feedback
also feel free to reach out over email, i'm inconshreveable at ngrok dot com
Hi @inconshreveable, happy user for many years and have done some crazy ngork remote setups to make systems like gitpod / docker work with ngrok.
Question for you - do you have a plan in mind for handling teams?
Right now it seems like the only way to handle it is with a manual naming convention:
https://{my-team-name}-{my-name}-api.ngrok.io
And then every single team member has to copy this convention by hand and you have to register webhooks, etc with these new routes.
It gets tedious fast.
Do you have ideas to work around this or register team members behind the scenes and still route traffic appropriately?
can you tell me a little bit more about what's tedious about it and/or the higher-layer problem you're trying to solve?
edit: feel free to email me as well at alan at ngrok dot com
Disclaimer: I'm currently incubating a similar product.
Honestly I would be very interested in hearing what you think the best plan for competing with Cloudflare Tunnel is. I've been keeping a close eye on this space for a couple years now, and Tunnel seems well on its way to dominating the mindshare.
It can be very hard to compete with a bundled loss-leader offering.
happy to chat more about our future plans offline, feel free to send me a note. i’m alan at ngrok dot com. would be curious to see what project you’re incubating!
hi folks, i’m the founder/creator of ngrok. happy to answer any questions.
we’ve got some exciting improvements we’re looking to share with the community very soon here
<3 to you all
inconshreveable commented on Exposing a web service with Cloudflare Tunnel erisa.dev/exposing-a-web-... · Posted by u/geostyx
I would rather use ngrok for these things: https://ngrok.com/
The reason why is because Alan is awesome.
Thanks Kord! Founder of ngrok here, just a quick note of correction for others in this thread: ngrok is absolutely intended for production use cases. There are many customers both hobbyist and enterprise running thousands of production workloads over ngrok's service (including ourselves! we dogfood ngrok for our ingress). We're excited to be sharing more about that with the HN community really soon.
Also, ngrok's support for introspection of data flowing over the tunnel was what got me to be a paying user of ngrok. Surprise! Their docs didn't mention it doesn't work for https tunnels. If their docs had been competent I probably would still have become a paying subscriber but I would have been a much less pissed off paying user than I was after subscribing, burning time trying to figure out what I was doing wrong, and finally concluding that feature didn't work. Oh, and ngrok support has never even acknowledged receipt of a single email, much less provide actual support. If you want people to pay, you need to treat it as a business not a hobby.
Really sorry about the frustrations! We're working on improving both of those pain points (as well as many other things). If you're still an ngrok user, send me an email at alan at ngrok dot com
we're excited to continue bringing the magic of ngrok to production workloads. there's no networking to configure, just helm install it. and unlike other ingress controllers, it creates secure internet ingress no matter where your clusters are: EKS, GKE, k3s on your raspberry pi, minikube on your laptop, OpenShift, etc.
<3s to you all