tmux_command doesn't seem to respect server

[pitosalas]

My tmux_command is being executed locally. I want it to first ssh to the server and then execute. How come is that not happening? It seems to defeat the purpose. In other words, it seems like the key use of tmux in this scenario would be to have a pane showing what's happening on server A and another one for server B. Especially if the last step on Server A is a long running process (e.g. httpd) that is handling requests. Or am I thinking of this wrong?

[pblesi]

Tmux itself is not inherently multi-server, as such runbook is a wrapper on top of tmux and each tmux pane is a shell that is executed locally. There is a possibility to create something like a remote tmux page that would handle the lifecycle of sshing to a remote host for tmux command execution. Nothing like this exists currently.

One option for this is to use the command argument that can be passed to tmux layout panes: https://github.com/braintree/runbook#tmux-layouts

This command could be responsible for ssh'ing to the remote host. You would likely want to make sure this command is reliable in this case, by having the ssh command always accept unknown host keys, etc.

Does this answer your question?

[pitosalas]

Hi Patrick

Yes absolutely!

Pito Salas Brandeis Computer Science Volen 134

On Feb 10, 2020, at 9:51 PM, Patrick Blesi notifications@github.com wrote:

Tmux https://github.com/tmux/tmux itself is not inherently multi-server, as such runbook is a wrapper on top of tmux and each tmux pane is a shell that is executed locally. There is a possibility to create something like a remote tmux page that would handle the lifecycle of sshing to a remote host for tmux command execution. Nothing like this exists currently.

One option for this is to use the command argument that can be passed to tmux layout panes: https://github.com/braintree/runbook#tmux-layouts https://github.com/braintree/runbook#tmux-layouts This command could be responsible for ssh'ing to the remote host. You would likely want to make sure this command is reliable in this case, by having the ssh command always accept unknown host keys, etc.

Does this answer your question?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/braintree/runbook/issues/33?email_source=notifications&email_token=AAAK5COBBKNK4WCM55GO57TRCIHDNA5CNFSM4KSCJCAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELLCBQA#issuecomment-584458432, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAK5CKXCQBH7OYH2KW4UVTRCIHDNANCNFSM4KSCJCAA.