SSHing into your running docker containers to edit code
no, not primarily
A few use cases:
1) I'm on a bastion host, and I need to knock up a script to run there
2) I'm working at home, and I don't want turn on the VPN, I SSH into my workstation and develop as if I was on the workstation
3) I need to change a conf/script/other because something is wrong, and the edit->commit->change config run-> test cycle is more than 2 seconds.
4) I'm in a container, debugging something and I want to edit a file (mostly python here so no need to compile) docker build-> run -> retry is painfully slow, and leaves loads of mess.
5) I'm working on a headless box somewhere or other.
6) I'm debugging on someone else's workstation
I only really work with vim in a terminal, so doing it over SSH isn't actually all that noticeable. It does gets to be a problem when the latency is > 200ms
Comments
no, not primarily
A few use cases:
1) I'm on a bastion host, and I need to knock up a script to run there
2) I'm working at home, and I don't want turn on the VPN, I SSH into my workstation and develop as if I was on the workstation
3) I need to change a conf/script/other because something is wrong, and the edit->commit->change config run-> test cycle is more than 2 seconds.
4) I'm in a container, debugging something and I want to edit a file (mostly python here so no need to compile) docker build-> run -> retry is painfully slow, and leaves loads of mess.
5) I'm working on a headless box somewhere or other.
6) I'm debugging on someone else's workstation
I only really work with vim in a terminal, so doing it over SSH isn't actually all that noticeable. It does gets to be a problem when the latency is > 200ms