trayscale VS ngrok

There's something like this. I try but my internet stop working when I use that. https://github.com/DeedleFake/trayscale

I've actually just recently used this with both pointer and value reveivers in one of my own projects.

I've got a project that depends on Libadwaita 1.2. The ubuntu-latest runner is 22.04 which only has Libadwaita 1.1 available in its repos, causing all of my CI runs to fail. I don't use Ubuntu personally so maybe this is something I can fix via APT and I just don't know how, but what's the recommended procedure for handling a situation where the runner's version of a dependency of a project is out-of-date? I couldn't seem to find anything in the official documentation or anywhere else via Google.

Source: I deal with this myself quite a bit with the Gtk4 bindings I use for one of my projects.

Here's an actual module that I work on as an example.

I've tried a number of them over the years but my latest attempt at a GUI project uses Gtk4.

#1: Introducing Tailscale SSH | 13 comments #2: Tailscale devs sometimes contribute to Headscale #3: I got annoyed at the lack of a Linux GUI, so I built one myself. It's not finished by any means, but it can at least list peers and their IPs. | 1 comment

Yep. I was using manual WireGuard tunnels for that, but everytime I added a machine I had to configurations from both sides with manual key swaps, plus the fact that it I wanted direct connections between each machine the configuration would literally have increased exponentially. Tailscale handles all of that for me. Literally. It's primarily an automatic WireGuard tunnel coordinator. I just have to install it and log in and voila, it just works. I like it so much that I've actually got a project that wraps a GUI around Tailscale for Linux.

This is very likely. I've been writing a GUI wrapper for the Linux Tailscale client, and part of what I interact with from their libraries uses generics. In particular, they've got a views package that implements immutable containers.

ngrok 1.0 - Original version of ngrok. No longer developed in favor of the commercial 2.0 version.

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

ngrok

if you're worried about the line "ngrok captures and analyzes all traffic over the tunnel for later inspection and replay" in https://github.com/inconshreveable/ngrok, I'd say that's a valid concern but not for ssh if you make sure the client knows what the host key is and does not accept a different one

Looks like it's open source so it could be just a fork away https://github.com/inconshreveable/ngrok

To get a fix domain, we can deploy HTTP tunnel in our own server. ngrok also provides an open source version for server side deployment. But it is old 1.x version and not recommended to deploy at production with some serious reliability issues.

I ended up inspired by ngork structure here: https://github.com/inconshreveable/ngrok it doesn't really work well with go modules, since i will end up running project like this:

Maybe https://github.com/inconshreveable/ngrok/issues/408

In Go, inconshreveable/ngrok and coyove/goflyway is well known, especially ngrok is popular among developers as a SaaS service.