3 ms·
I don't think I was clear, sorry. I meant I rarely use it on remote servers, I rarely have the need for that process. I only have a need to do dev locally and
by TomAnthony 11y ago
I don't think I was clear, sorry. I meant I rarely use it on remote servers, I rarely have the need for that process.
I only have a need to do dev locally and was using tmux on my local machine. I know several other devs who only use tmux in this fashion.
I know many people use it when they are on a remote machine via ssh - what are the usual activities that require someone to be ssh'ed in doing complex tasks directly on a remote machine?
- riquito 11y agoThe most common thing that comes to mind is altering huge database tables. You may need from minutes to hours to perform heavy SQL operations and if you run your commands from a client you want it to survive the ssh session, no matter what. Another example is the import/export of large quantities of data (e.g. to clone/move a machine) or perform a long running task (e.g. you found a better way to compress images and want to run it once on every image). Of course these are not everyday tasks, but once in a while they may be required. That said, if you connect via ssh to a server you are rarely happy to "lose" whatever task you have run, there aren't major drawbacks in using screen/tmux everytime you connect to a remote server.
- msvalkon 11y agoWhere I work, most of our development (includes building, testing and packaging) is done on remote machines to which we ssh to. Few people prefer gui ide's so most ssh and then run vim or emacs. Having tmux on the server hub is pretty convenient. Especially nice if you want to run a set of tests over night.
- TomAnthony 11y agoWhat is the advantage to development being done on remote machines? Forgive me if I'm missing something obvious - it just seems quite different to the paradigms I've seen in 'the real world'.