Vscode: Request: Open remote folder via SSH

[PunchyRascal]

It would be very nice if VS Code could open a remote folder, found via SSH connection.

Currently I have to use linux Samba share, that is mounted in Windows and it is rather slow - especially for searching and quick opening files.

It would also resolve problems with versioning, because linux symlinks don't work on Windows (and windows symlinks don't help), changes checking is slow etc.

[bpasero]

There are probably duplicates.

[pwwang]

+1

[PunchyRascal]

I searched the issues, but found nothing similar, but could have overlooked it.

[rumatakira]

+1

[booooh]

+1

[uberthought]

+1

[jpldev]

+1

[skunchamwar]

+1

[jcooklin]

+1

[nagarakesh4]

+1

[tanakh]

+1

[PunchyRascal]

Guys read the guidelines for upvoting issues: https://github.com/Microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions

[ofanidariyan]

+1

[ewright3]

+1

[iamlaobie]

+1

[waterdeng]

+1

[vsoaresz]

+1

[PunchyRascal]

Use thumbs up on the original post, do not add +1 comments

[visitantz]

Exactly what needed, now my work flow is open a vscode on VMware Lubuntu SSH connection.

[sourcepirate]

+1

[PatrikNordberg]

Any progress on this feature?
I would really like this as well.
Now I use SFTP Net Drive to connect my remote folder as a local drive.
Would be much better if VSCode could handle this internally.

[PunchyRascal]

Maybe if you can, try setting up your remote drive as a NFS share - it is
faster than samba (if that's your case).

On 4 December 2017 at 13:09, Patrik Nordberg [e-mail]
wrote:

Any progress on this feature?
I would really like this as well.
Now I use SFTP Net Drive to connect my remote folder as a local drive.
Would be much better if VSCode could handle this internally.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/27423#issuecomment-348944445,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAyIGGxt9L3fYeoAnODlBqpVlJctPrQqks5s8-EFgaJpZM4NpF7G
.

[devmckeon]

(this is not in response to anyone or any reply, just a suggestion of perspective)

I think we can all agree that there are always ways to do this from outside vscode. However, opening remote folders over ssh is a very useful feature for a light-IDE slash text-editor. I've heard from colleagues that I've tried to convince to use Code, who've said that they simply would not try anything that didn't have such a feature. I think it's wise to accept that this is a productivity boosting feature that many people feel is essential, and that it's unwise to write-off those users with rationalizations of the form: "that should not be your workflow", or "that's not the way to do it right". Perhaps in a different world, everybody would simply be a command line natural, and be able to mount remote drives as easy as changing directories.

Also, I would like to shrink the list of things Atom does that Code does not. =) And this remains of the things I miss from other editors.

[chenqinkai]

Any progress on this feature ?

This is a feature needed by a lot of developers who work on remote server and it is a pity that we can only use vim or emacs instead of this modern and excellent editor. We would really appreciate it if vscode could support this feature.

[kvn1351]

+1

This would make my VM development so much more pleasant.

[firelizzard18]

@kvn1351, do not +1; doing so is useless. Thumbs up the initial comment/issue description.

There was a similar request to be able to remotely edit files via SSH (#23076) that for some reason was closed as a duplicate of allow reading from stdin (#7320/#6161) even though those issues really don't solve the edit-via-SSH issue.

[benlindsay]

Any progress on this? Remote coding and compiling on a research cluster is a big part of my workflow. Using sshfs to mount folders I can do the editing part ok, but it would be nice not to have to run that extra command. Additionally, it would be great if I could point VSCode to a remote compiler and debugger to build, run, and debug my code from within the VSCode environment.

P.S. Thanks for the work you all do! VSCode is great.

[firelizzard18]

@benlindsay The latest major update to VSCode (I believe 1.23) added a FileSystemProvider API (or something like that). With this API, issues like this one and #44378 can be implemented with extensions.

Unfortunately, to date, I have not found an extension that does a good job of this. Given that this API has not been available for long, I expect better things in the future.

[firelizzard18]

@jrieken This issue should be closed as an extension-candidate, now that the file system provider api has been shipped

[jrieken]

True story - there is now API that allows extensions to add a different file system to VS Code. There is also some impressive extension out there, eg. https://marketplace.visualstudio.com/items?itemName=mkloubert.vscode-remote-workspace.

[vscodebot[bot]]

We try to keep VS Code lean and we think the functionality you're asking for is great for a VS Code extension. Maybe you can already find one that suits you in the VS Code Marketplace. Just in case, in a few simple steps you can get started writing your own extension. See also our issue reporting guidelines.

Happy Coding!

[mjbvz]

We just announced remote development with VS Code, check out the blog post for details