A few days ago I came across the solution to a workflow issue I had been for long wishing could be done. Today I solved another one, and since they’re connected, I outline them below. Maybe they’ll make someone’s day! 🙂
I often work with remote servers that are almost always some flavor of Linux, most frequently Ubuntu/Debian, but also CentOS/Redhat. Despite of being a lifelong geek, I really dislike
vi, finding it massively unintuitive. Maybe I haven’t figured out its intricacies, but I doubt it – it just doesn’t jive with me. In the 90’s I remembered most of Emacs’ chords by heart (or more likely by muscle memory), and really enjoyed using it, but for some reason I eventually stopped using it and only now am picking it up again. For now, however, my go-to editor in Linux is
joe, which is handy enough (more so than
nano), but none of them still are as comfortable and flexible to use than a good GUI editor. In Windows & macOS my editor of choice is Sublime Text 3, and a few days ago I came across this answer in StackOverflow. Enter rmate/rsub! To make the magic happen, first install a small
rmate script on your server (but call it
rsub since you’re using Sublime Text rather than TextMate):
sudo curl -L --output /usr/local/bin/rsub https://raw.github.com/aurora/rmate/master/rmate
sudo chmod +x /usr/local/bin/rsub
Then add a few lines in
~/.ssh/config on your Mac (Windows users, keep reading, you haven’t been forgotten):
RemoteForward 52698 127.0.0.1:52698
To exclude some domains where you’ll never use
rsub, like GitHub:
(the significant line above is
rsub package in Sublime (easiest done with Package Control), and now
rsub someFileName command on the remote opens
someFileName in Sublime on Mac! Like magic!! No need to mess with FTPS. Just one word of caution.. if you put the Mac to sleep, the “rsubbed” file may become disconnected from the remote, so when you make the first save after resuming work, verify that the changes are indeed saved, or close the file and reopen it from the remote.
rsub also works with Sublime Text in Windows. The only part of the above setup that differs on Windows is the SSH config since Microsoft’s effort to create a native OpenSSH port for Windows is slow going (“non-production ready pre-release v0.0.17.0” with 161 open issues as of writing of this post). I usually use the excellent commercial SSH client VanDyke’s SecureCRT as the SSH terminal in Windows. I initially thought reverse port forwarding would not be possible in it, but alas, I stand corrected! Van Dyke’s always helpful and knowledgeable technical support pointed out how to achieve the desired port forwarding in it (the config section in question was titled: “Port Forwarding – Remote/X11”, and that indeed meant “remote OR X11”, not “remote X11”, as I had read it. So regardless of whether you use PuTTY (or its derivatives like KiTTY) or SecureCRT, you setting up the port forwarding is a snap. I’ll outline below PuTTY’s setup first, then SecureCRT’s equivalent configuraiton.
Install and fire up PuTTY. Just to make sure you start from a clean slate, click on “Default Settings” and then “Load”:
Set the name (or IP) of the server you’ll be running
If you’re not using PuTTY’s key agent Pageant to authenticate, enter the path for your private RSA key. Note that it must be in
PPK format (if you have PEM format key, you need to convert it with PuTTYgen, another PuTTY utility program):
Add the remote listener port:
[OPTIONAL] If you’re NOT using this PuTTY session for the shell (i.e. if you’re using for that purpose some another program that lacks the reverse forwarding capability), disable the shell for this connection:
[OPTIONAL] Similarly, if you’re not using this PuTTY session for the shell, set the window size to a small value:
Finally, back in the Session tab, save the session: give it a name, then click on “Save”. If this is a shell-less RSUB session only, give a descriptive name:
Now you have configured a RSUB session in PuTTY. For convenience, you may want to create a desktop link to activate the [RSUB] session. If so, right click on the desktop and select “New > Shortcut”, then enter the path to
putty.exe, followed by
-load, and the name you gave the session in PuTTY:
Finally, give a descriptive name for the desktop link:
And now you have a link that opens the RSUB channel to your remote server:
Click on it, and it opens a small session window. As long as you keep it open, you can use the
rsub command on the remote to open and edit remote files on your local Sublime Text!
And now, the same for SecureCRT:
Once you have configured a profile otherwise (set the hostname, username, and authentication information – [preferably] either a PEM format key, or a password [if allowed by your server]), head to Connection > Port Forwarding > Remote/X11, like so:
Click on “Add”, and enter a name for this tunnel, such as “RSUB” here, and the port 52698. When you enter it in the “Remote > Port” field, the “Local > Port” is automatically filled out for you:
And now you have the
rsub port forwarding in place in SecureCRT!
Now when you open the session, you automatically have a
rsub port open as well, and once you open Sublime Text on Windows, you can proceed to type
rsub someFileName on the server, and it opens in Sublime.
So far so good (remote editing is working great!). Today I needed to diff an old configuration file against the new one, and the CLI
diff output was too tedious to decipher. Then it occurred to me that maybe it would be possible to somehow use my favorite GUI diff utility, Beyond Compare with Sublime — and it is! The only thing to note is that when you open Beyond Compare from the files open in Sublime, you’ll need to save the completed diff first in Beyond Compare, and then in Sublime. Note that the file change indicator doesn’t light up in Sublime even when it has received the changes resulting from the diff reconciliation in Beyond Compare. The changes are received in Sublime when you save them in Beyond Compare, but not saved from Sublime [to the server over
rsub] until you explicitly hit save in Sublime.
Now.. the files opened in Sublime from a remote using
rsub can be diffed by this method with Beyond Compare! Working with remote files just became a lot more fun! 🙂
Update 2017-11-07: The article was updated with the latest
rsub installation details, and PuTTY configuration instructions were added.
Update 2017-11-09: Van Dyke’s technical support pointed out to me that the reverse port forwarding can be accomplished in SecureCRT as well, so I corrected the article, and added the configuration details for SecureCRT.