wetty

ttyd is a nice little web terminal: https://github.com/tsl0922/ttyd Just a small, fast, low fuss C-based executable. wetty is another good option if you want to run a nodejs server: https://github.com/butlerx/wetty Both use xterm.js for the client terminal, which is these days the only game in town for a web terminal (it's what VS code and many other electron apps use too). It's quite good. Do be aware though that running a web-accessible terminal is a huge security headache. You're opening up a websocket to effectively allow commands and code to run on your server. Pay attention to security and authentication options any web terminal gives you, and use them. Most are not very secure out of the box or just following their readme examples. And watch out as many rootkits use web terminals as payloads so smart organizations and security

I used wetty for this: node server, but like this uses xterm.js client https://github.com/butlerx/wetty Though only locally, not connected to the internet. Maybe I'm paranoid, since I use so much other software without auditing, but somehow I feel especially vulnerable to web terminals, aside from anyone being able to login, and public keys not being convenient on the web. Also, the readme.md for rtty here suggests running as root.

If you want to run commands on the raspbi from the web, you have lots of options. The question is if you want to send the commands literally to the terminal, or have some preprocessing step in between? If you want to have a preprocessing step, then you need an API to take the commands, process them, run them, and then return the output. If you want to stream the output, you should look into something like websockets. There are also libraries built specifically for streaming logs to the browser, e.g. [0] But might I suggest a simpler approach? How about a JS terminal emulator that is SSHed into the raspberry pi? I've used a library called "wetty" [1] successfully in the past. It's a node server + JS terminal emulator (based on hterm, used in chromebooks). The node server SSH's into the target box on behalf of the client, and then forwards

I would be dead without `wetty` https://github.com/krishnasrinivas/wetty. Now I also love Cloud9 https://aws.amazon.com/cloud9/

I've had a very positive experience with wetty[0] which uses the ChromeOS terminal emulator (hterm) on the client side, and communicates via websocket to a small node server that makes the SSH connection. I use it to provide a shell into an internal docker container used for managing some things. Everything "just works," even tmux key bindings. [0] https://github.com/krishnasrinivas/wetty

Taking it for a test drive after thinking "nope." I predictable wanted a terminal.. my solution was grabbing a copy of wetty (https://github.com/krishnasrinivas/wetty), and adding a commander button to run wetty and browser set to the wetty url, and now I've got a terminal. pop one off the yak stack..

I've had good luck with wetty: https://github.com/krishnasrinivas/wetty It seems reasonably stable and fast, I suspect because it leverages the hterm terminal emulator that's built into ChromeOS. May not work on Windows or OSX though.

I access through http/https using [Wetty](https://github.com/krishnasrinivas/wetty) within a electron shell and it works perfectly!

I use Wetty. It is too good and gives a near native terminal experience. Link below .. [krishnasrinivas/wetty: Terminal in browser over http/https. (Ajaxterm/Anyterm alternative, but much better)](https://github.com/krishnasrinivas/wetty)