This could simplify RL on ncurses codes.
What is RL referring to?
Potentially readline? https://en.wikipedia.org/wiki/GNU_Readline
ht: Headless Terminal
21–30 of 90 posts
Re: ht: Headless Terminal
#22Hmm this may have some use cases for macOS automation where there’s no MDM.
Re: ht: Headless Terminal
#23i dont see any way of actually typing key presses, like modifiers.
This project looks pretty interesting, maybe i'm missing something.
Re: ht: Headless Terminal
#24Re: ht: Headless Terminal
#25Reading the readme, I find myself wondering what problems this solves for. The example of wrapping nano strikes me as particularly odd, since editing files is already fairly easy to do programmatically either via direct file operations or with tools like sed. Aside from editors, most tools that offer a tui also expose the functionality for programmatic access (typically with some additional flags to the same binary).…
I had this issue of needing to control Docker containers in a VPS, without sharing access to the server itself. It seems like it will be easy to create a simple web service that can communicate with the ht API, list my containers, show me the stats, and restart containers if I want to. I can manage all security in the web service. This could be a nice case.
That would work but wouldn't making http requests to the docker socket itself be a little easier?
Example:
curl --silent --unix-socket /run/user/1000/docker.sock http://v1.41/version
You could even do something like a reverse proxy to very limited paths although I tend to think that would ultimately be a bad idea and making your own http calls is probably better.
Re: ht: Headless Terminal
#26Reading the readme, I find myself wondering what problems this solves for. The example of wrapping nano strikes me as particularly odd, since editing files is already fairly easy to do programmatically either via direct file operations or with tools like sed. Aside from editors, most tools that offer a tui also expose the functionality for programmatic access (typically with some additional flags to the same binary).…
here's a terrible script which runs as root on all my boxes (as `redirect-tty /dev/tty1 unl0kr`): https://git.uninsane.org/colin/nix-files/src/commit/9189f18c...
none of the Linux greeters meet all my needs, so i fall back to `login`. but i still need a graphical program for actually entering in my password -- particularly because some of my devices don't have a physical keyboard (i.e. my phone). so i take the output of a framebuffer-capable on-screen-keyboard [1] and pipe that into `login`. but try actually doing that. try `cat mypassword.txt | login MobiusHorizons`. it doesn't work: `login` does some things on its stdin which only work on vtty. so instead i run login on /dev/tty1, and pipe the password into /dev/tty1 for the auth.
yes, this solution is terrible. a lot of things would make it less terrible. i could fix one of the greeters to work the way i need it (tried that). i could patch `login` (where it probably won't ever be upstreamed). i could integrate the OSK into the same input system the ttys use... or i could reach for `ht`. everything except the last one is a day or more of work.
1: https://gitlab.com/postmarketOS/buffybox/-/tree/master/unl0k...
Re: ht: Headless Terminal
#27Super cool! Also super difficult to secure if used server-side…
Re: ht: Headless Terminal
#28How does this relate to classic tools like `expect`?
I don't think you can reasonably use expect with TUIs, but you can use this with TUIs.
Re: ht: Headless Terminal
#29Re: ht: Headless Terminal
#30Earlier quoted context omitted.
I had this issue of needing to control Docker containers in a VPS, without sharing access to the server itself. It seems like it will be easy to create a simple web service that can communicate with the ht API, list my containers, show me the stats, and restart containers if I want to. I can manage all security in the web service. This could be a nice case.
That would work but wouldn't making http requests to the docker socket itself be a little easier? Example: curl --silent --unix-socket /run/user/1000/docker.sock http://v1.41/version From: https://dev.to/smac89/curl-to-docker-through-sockets-1mhe You could even do something like a reverse proxy to very limited paths although I tend to think that would ultimately be a bad idea and making your own http calls is probabl…
You probably don’t want to expose that service to the internet…
I see this as something like the console management for VPS. Back in the day, I remember reading about how prgmr.com had setup a console that you’d directly SSH into. That’s now this interface [1] (and a company name change), but I could see how programmatically working with this would be helpful.