Since Windows 10, Windows is shipped with an optional built-in OpenSSH server.
This is a great news, since I am used to dev on my Linux environment and with this built-in SSH server, I should be able to keep my daily tools (a shell and the Vim editor) to get the work done on my servers.
Configuring the SSH access was pretty easy, by default the password and key authentification are enabled, creating a .ssh/authorized_keys under my user home on the Windows machine was enough for my needs.
Powershell as default SSH shell
The SSH server runs cmd.exe as default shell, it can be changed via a registry entry.
Remote file edition using vim
Vim comes with a feature to edit remote file using SCP. The syntax is described there.
But the issue here is that Windows and Linux are using different path syntaxes and escaping methods.
Below are the different syntaxes that I ended up with when trying to access my remote files.
There are most likely better ways to achieve this but still, I was quite happy to not have to use anymore remote desktop UI tools nor shared folders to work on my Windows dev machines.
If you have anything better, feel free to send me an email at fda@rudder.io
