localtunnel VS inlets-archived

localtunnel/localtunnel - Written in node. Popular suggestion.

Thanks for the history. I maintain this list[0], and wasn't aware of OG localtunnel, likely because there's a somewhat newer and now more popular project with the same name[1]. You appear to be correct on timing. Here's the earliest commits on GitHub for each of the projects:

OG localtunnel (2010): https://github.com/progrium/localtunnel/tree/fb82920d9d3e538...

Other localtunnel (2012): https://github.com/localtunnel/localtunnel/tree/93d62b9dbb9f...

ngrok (2012): https://github.com/inconshreveable/ngrok/tree/8f4795ecac7f92...

I'll see that OG localtunnel gets added to the list for posterity.

[0]: https://github.com/anderspitman/awesome-tunneling

[1]: https://github.com/localtunnel/localtunnel

These is a very common problem. Luckily, it's been solved already. My go-to tool for this was ngrok or localtunnel. Both of these tools are great, but they didn't fit my needs perfectly.

localtunnel — Expose locally running servers over a tunnel to a public URL. Free hosted version, and open source.

Localtunnel used to be a nice tunnel. It has gone through some enshittification lately.

> tunnel consent page now requires the tunnel creator's public IP in order to access tunnel content

https://github.com/localtunnel/localtunnel/issues/598

There are free non kafkaesque competitors out there.

I recently went through having to tunnel my development environment to setup an oauth2 flow for a rails integration. I found that using https://github.com/localtunnel/localtunnel was a better fit.

I prefer localtunnel: https://github.com/localtunnel/localtunnel

There's also Local Tunnel (http://localtunnel.me)

Not sure if it works combined with ngrok: https://www.npmjs.com/package/localtunnel

inlets - Used to be open source; now focused on a polished commercial offering. Designed to work well with Kubernetes.

This appears to be a very old version of the project before it was eventually forked to a repo that belonged to the inlets org on GitHub. That's why when Alex deleted the github.com/inlets/inlets-archived repo yesterday (a fork he controlled, where all the work since late 2018 was done), this repo under the-cc-dev now appears as the root repo of all the forks that exist right now, including my fork (https://github.com/mattwelke/inlets-archived).

Also if you're looking to self host something checkout inlets: https://docs.inlets.dev/#/

I've used Hamachi (vpn.net), that worked pretty well. You could also try Inlets (https://github.com/inlets/inlets).

Did you check https://github.com/inlets/inlets ? It’s an opensource alternative to cloudfared. Never use it myself but creator has a good track-record of developing nice oss solutions (were raspberry is usually first-class citizen)

I found some of them that are related to this topic, it might be useful for you too: * inlets * kt-connect * shuttle * ngrook

You could build something similar to HCM yourself. For instance you can use Inlets but you'd have to maintain the server yourself and pay for it. Plus, HCM is a breeze to set up and can be automated with the Azure CLI