wetty VS ssh-pageant

WeTTY

I use wetty for a terminal in a browser. https://github.com/butlerx/wetty

You’re already running docker. Install Wetty. Works great. Make sure you have strong strong Auth though.

Can RGNets look into integrating Wetty, terminal over https (https://github.com/butlerx/wetty) where we can ssh to devices it manages from the fleet or the rXg itself without giving direct shell access to users.

ttyd is a nice little web terminal: https://github.com/tsl0922/ttyd Just small, fast, low fuss C-based executable.

wetty is another good option if you want to run a nodejs app: 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.

Do you mean something like Wetty?

Hello, does anyone know of an open source project/web app/library, written in Haskell, that makes terminal interface accessible via browser? An example of what I'd like to achieve: Start R repl process withing a docker container on the backend (e.g. `docker run -it --rm rocker/r-base`) and allow user to interact with it using terminal-like interface from their browser (with stuff like TAB completion working etc.) It seems that xterm.js is a popular choice to implement the client side of such a thing, but I'm looking for some inspiration of how a backend of such an application could be implemented in Haskell. Examples in other languages that do similar thing to what I'd like: Go: https://github.com/yudai/gotty Typescript: https://github.com/butlerx/wetty

Then, for some special situations (e.g. running a suite a few tools that are useful for me and some other devs on my team), the quick solution is to simply just setup a Dockerfile based on alpine:latest and install the other tools/apps I need that require SSH key forwarding, like capistrano. I already have putty agent running on my host machine with ssh-pageant which connects my Cygwin instance to that. But anyway, on the container, I just setup basic sshd there, login with keys and enable agent forwarding and then run my tools there that then hop on to the remote server (using my forwarded agent).