GateOne VS webssh2

It was Gate One: https://github.com/liftoff/GateOne

(Note: Company no longer exists so it is unmaintained, fork at will =)

It's been so long since I've looked at the code but I did write excellent documentation, most of which is generated from docstrings. Example:

https://github.com/liftoff/GateOne/blob/master/gateone/core/...

You can read the documentation here:

https://liftoff.github.io/GateOne/

If you look at the bookmarks plugin you can see an example of how I performed this style of client<->server synchronization using an Update Sequence Number (USN):

https://github.com/liftoff/GateOne/blob/6ae1d01f7fe21e2703bd...

After the web client connects to the websocket all the plugin's `init()` methods are called and the bookmarks plugin's javascript file calls `userLoginSync()`:

https://github.com/liftoff/GateOne/blob/6ae1d01f7fe21e2703bd...

It sends the current USN (which is retrieved from `localStorage`) to the server (the routing is quite sophisticated... Just know that the message ends up going to the correct function =) and if it's different from the USN on the server the server will send an updated list of bookmarks to the client at which point the client will take care of that via its own handler:

https://github.com/liftoff/GateOne/blob/6ae1d01f7fe21e2703bd...

If you examine the bookmarks.js from top to bottom (it's not THAT long) you should get the gist of where and how various states are stored. That plugin mostly deals with stuff in `localStorage` but if you poke around in Gate One you'll see vastly more sophisticated state synchronization and state update routines at work.

or GateOne

GateOne is also fantastic for this too!

GateOne is nice, can also be run in docker

You can also do it using gateone to emulate a full terminal. https://github.com/liftoff/GateOne

Something like this might be a better approach. Or there's GateOne which could do whatever you needed it to, I'd imagine.

I’ve worked with WebSSH2 in the past. Worked well for me. It’s a little tricky to set it up behind a reverse proxy.

You may need to do some more research. SSHD can run on an HTTP port, but why bundle a web server and additional protocols into something? There are web based ssh clients - https://github.com/billchurch/webssh2 - simple google search.

Plenty of "neckbeards" understand containers and probably understand the underlying technologies (cgroups, etc) as well as comparable (or historical) approaches (jails, zones, etc) better than most.

But, because something doesn't cater to your whims, must complicate things that actually work.

https://github.com/billchurch/WebSSH2 which allows to SSH to containers from the web.