6 ms·
https://tunshell.com/ https://tunshell.com/ works great for *nix runners. I made https://github.com/nelsonjchen/reverse-rdp-windows-github-actions https://gith
by crazysim 5y ago
https://tunshell.com/ https://tunshell.com/ works great for *nix runners.
I made https://github.com/nelsonjchen/reverse-rdp-windows-github-actions https://github.com/nelsonjchen/reverse-rdp-windows-github-ac... for the Windows runners.
Just add continue on error to the failing step and use temporarily use these kinds of tools in the next step(s).
- kevincox 5y ago> https://tunshell.com/ https://tunshell.com/ works great for nix runners. Oh and their interface is a `curl | sh` that execs whatever happens to be lying around in `/tmp/tunshell/client`. I guess* that is probably fine on a single-user system but I prefer not to run binaries that just about every process on my system can write to. https://lets.tunshell.com/init.sh https://lets.tunshell.com/init.sh Edit: I filed a bug https://github.com/TimeToogo/tunshell/issues/19 https://github.com/TimeToogo/tunshell/issues/19
- derefr 5y ago> I guess that is probably fine on a single-user system Most of these services run your workload inside a container, so it's not even a single-user system; it's an ephemeral system. It's like anything's going to be there other than the base image + what you put there.
- kevincox 5y agoThis same script is used for the server and client. So you are running this on your workstation.