I don't have a strict idea of "done" for ut. But, I am not keen on adding increasing complex things to it either. It's purpose is convenience not exhaustiveness.
The point of ut is not to replace or invent new tooling. It is meant to be a set of tools that are simple, self exploratory and work out of the box with sane defaults. So, essentially, something that you don't have to remember syntax for or go through help/man pages everytime you want to use it.
This looks awesome, thanks! The best thing about this imo is that I can remember the url instead of having to dig through pages to find the official pinout pdf.
I wanted to start using golinks in my workflow and I am a fan of the duckduckgo bangs. So, I built a Rust based web server that can act can act as your default search engine and handle bangs and go links for you.
Have not played around with it, but, curious, how does debugging on production work for a specific request/session? Can I filter by some sort if request trace id or something?
Yup, wormhole and portal are better in most aspects. Beam is helpful when you have novel constraints like not being able to install arbitrary binaries, or if you have the need to transfer streams and not just files, or maybe even pub key based white-listing of access.
You can do this using a regular SSH server and some elbow grease. This is meant to be a simple setup and forget system that is relatively locked down and doesn't expose any more functionality than strictly necessary.