cfg/env/prod
Dustin d989994f25 serterm: Deploy serial terminal server
The serial terminal server ("serterm") is a collection of scripts that
automate launching multiple `picocom` processes, one per USB-serial
adapter connected to the system.  Each `picocom` process has its own
window in a `tmux` session, which is accessible via SSH on a dedicated
port (20022).  Clients connecting to that SSH server will be
automatically attached to the `tmux` session, allowing them to access
the serial terminal server quickly and easily.  The SSH server only
allows public-key authentication, so the authorized keys have to be
pre-configured.

In addition to automatically launching `picocom` windows for each serial
port when the terminal server starts, ports that are added (hot-plugged)
while the server is running will have windows created for them
automatically, by way of a udev rule.

Each `picocom` process is configured to log communications with its
respective serial port.  This may be useful, for example, to find
diagnostic messages that may not be captured by the `tmux` scrollback
buffer.
2024-03-21 21:24:12 -05:00
..
fetchcert.cue loki: Use fetchcert to manage server certificate 2024-02-18 11:35:13 -06:00
instructions.cue env/prod: Collect common tempates in module 2024-02-03 11:16:52 -06:00
loki.cue loki: Deploy Caddy in front of Loki 2024-02-21 07:47:51 -06:00
nut.cue prod/nut: Require both UPS to be online 2024-01-25 21:12:33 -06:00
promtail.cue promtail: Update loki port 2024-02-21 07:47:51 -06:00
serterm.cue serterm: Deploy serial terminal server 2024-03-21 21:24:12 -05:00
ssh.cue app/ssh: Configure sshd trusted user CA keys 2024-02-03 11:16:52 -06:00
sudo.cue sudo: Configure pam_ssh_agent_auth 2024-01-29 09:10:42 -06:00