4 ms·
I've used a shared tmux session over ssh in the past, which worked quite nicely without installing any extra software (besides tmux obviously)
by W0lf 9y ago
I've used a shared tmux session over ssh in the past, which worked quite nicely without installing any extra software (besides tmux obviously)
- caiob 9y agoIs Wemux (https://github.com/zolrath/wemux https://github.com/zolrath/wemux) still relevant?
- mikekchar 9y agoNot the OP, but as a frequent tmux pair programmer, I've never found wemux to be particularly relevant. It's useful if you don't know how to use the advanced features of tmux. Everything in wemux can be done in tmux -- you just need to know how to do it. Having said that, reading the tmux manual is something that might occupy you for more time than you would like to spend :-)
- goerz 9y agoYeah, tmux is pretty powerful all by itself, and perfectly suited for pair-programming, assuming ssh is set up. I wrote a little wrapper script a while ago to handle the setup of the ssh keys on a temporary basis (the partner's SSH key is allowed to attach to the appropriate tmux session only and is removed when disconnected): https://github.com/goerz/tmuxpair https://github.com/goerz/tmuxpair
- mikekchar 9y agoI do something similar. I set up a "pair" user on the system whose login shell is just a script that attaches to the tmux session. The script that starts the tmux session, sets the group permissions on the socket to "pair". This means that even though the "pair" user has their ssh key in pair's authorised_keys file, they can't log in unless there is an ssh session with the appropriately shared socket. Also, they are never logged in as your user (though, sharing the session, they can do whatever you can do -- only you are guaranteed to be able to see it).
- be_erik 9y agotmate is fantastic for exactly this. You can share a session on your local machine, the pair doesn't need tmux, and obviously you don't need a remote machine setup for development. https://tmate.io/ https://tmate.io/