This might just be my shortest post ever in this blog, at least for now. At this early date it’s just a link to the Atom No More? blog post in my personal blog.

The note above indicates that this post superseeds 085-remote-atom, but there are other Atom-related posts that are also impacted.

Some of these include:

As time passes I’ll document here any work-specific changes I make to my new VSCode environments.

Replacing atom . with code .

The personal blog post mentioned above, Atom No More?, includes a procedure I used to implement code . to launch VSCode from a terminal window on any of my Mac workstations. As of this writing, June 22, 2022, I have successfully implmented this change on all of my Grinnell College workstations.

Replacing Remote Atom

Some time ago I documented my setup of Remote Atom which gave me the ability to type open an SSH tunnel from any workstation to a remote Linux host, like DGDocker1 or DGDockerX, and locally use my Atom editor to make and save changes to individual files remotely. The command was simple, ratom <filename> would do the trick.

VSCode can be setup to do the same kind of thing and I’m following guidance at Remote Development using SSH to do just that, starting with DGDockerX, the Docker node where we build and run the staging version of Digital.Grinnell.

It works, and the setup was easier than with Atom, and perhaps better in the end? We shall see, but so far it’s looking very good.


To begin this process I installed the necessary Remote Development extemsion pack. That was easy. Next, I opened my VPN connection to campus, as required for SSH, and then inside VSCode I did as I was told…

  • โ‡งโŒ˜P to open the command pallet,
  • entered Remote-SSH: Connect to Host... to initiate the command,
  • selected Add New SSH Host..., and
  • added DGDockerX using ssh -A

When prompted to save the above confituration I did so into my workstation’s ~/.ssh/config file. Now, to open a new connection to DGDockerX I just repeat the first two steps above, then pick from the list provided. That’s it. Once that is done I can open the VSCode explorer and navigate through the remote host as needed.


The process was exactly as above, so now when I want to edit files on DGDocker1, I just do this in VSCode

  • โ‡งโŒ˜P to open the command pallet,
  • entered Remote-SSH: Connect to Host... to initiate the command,
  • select from the pull-down list that’s presented.

And that’s a wrap. Until next time, stay safe and wash your hands! ๐Ÿ˜„