tmux: part of the TUI stack for BrainTrust

[JohnTigue]

One of the artifacts of this issue is the tmux wiki page.

There are multiple use cases where shared terminals would be useful:

• Learning together the ways of life on the command line (we could see what others are doing with SD on the CLI)
• Viewing console messages of web servers
• System dashboards in TUI sessions (See #113)

The latter is the current forcing function: after a web-ui SD app is spun up, if we want to look at the log messages, we need a way to attach to the session the SD app is running. That's pretty much what tmux was made for (amongst other things).

Also, since we now have EC2 Instance Connect set up, we could just ssh in as foo@manyhands.io from our local machine command line (DOS box, macOS Terminal, iTerm, whatever). Have tmux set up would be a nice way to have long running "session" that multiple people could attach to. The "sessions" would persist across folks being in the session, which is not normally the case with raw linux.

The tmux license is very permissive. All they ask is:

Copyright (c)

Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

[JohnTigue]

critmux: Docker + CRIU + tmux = magic!, with the tagline: "Freeze. Thaw. Repeat."

[JohnTigue]

Another – more direct – way to get the the A1111 command line would be via tmux and mssh. That would be 100% command line, not web browser involved. Admittedly that is more hardcore, but we'd have both the hardcore (CLI only way) and the friendly AWS Console way going. Here's the intro to mssh, Connect using the EC2 Instance Connect CLI.