ADM-GoTTY
Purpose
This software stack provides the TTY2Web fork of GoTTY, a small service for the server administration by accessing the Linux shell via a frontend Web service. Internally GoTTY accesses the server via the SSH service.
Properties
Stack-Description | GoTTY/SSH System Administration (ADM) |
---|---|
Stack-Image | docker.msg.team/ps/docker-stack-adm-gotty |
Stack-Version | 2.8.0 |
Stack-Release | 20230320 |
Product-Name | GoTTY/TTY2Web |
Product-Vendor | Iwasaki Yudai et al. |
Product-Contact | https://github.com/kost/tty2web |
Product-Model | Open Source |
Product-License | MIT |
Product-Limits | none |
Implementation Base | Go Programming Language |
Execution Base | ELF executable. |
Initial Start Time | 00:00:01 |
Documentation | https://github.com/yudai/gotty/blob/master/README.md |
Topology
The stack consists of 1 container:
- adm-gotty: the GoTTY application
Configuration
Variable Name | Default | Meaning | |
CFG_GOTTY_ADDR | host.docker.internal | Hostname or IP address to connect to through SSH |
See also the variables which control integration of the stack into the reverse proxy.
For changes to take effect the stack has to be reinstalled.
First Steps
Usually, there is no need to configure anything.
Once connected and authenticated the tmux session multiplexer is started. This allows you to run several sessions through the same terminal. If you don't need this just go ahead, aside from the statusline at the bottom you won't get affected. If you need several sessions you command tmux by hitting CTRL-B followed by a command character:
- CTRL-B c creates a new session (issue exit in this shell to terminate the session)
- CTRL-B n with n being a number from 0 to 9 switches to this session (see the status line at the bottom for the existing sessions)
- CTRL-B l switches to the previous session (if you have just two sessions it will switch between those)
- CTRL-B d logs you out but will keep all your sessions in their state. When you log in once again later you will find all your sessions as if you never have left. Overmore, if commands were executed in some sessions the continue even you have logged out. This is great for triggering some long-running stuff, log out and return later to see the progress without having the need to keep the terminal window open. Also if you get logged out due to connection problems sessions are kept until you return.
If you want to know more check out one of the various tmux tutorials on the Net or spend a few minutes to view this video.
Related Documents