As discussed in #196 and #240, Microsoft's proprietary Remote extensions aren't usable in OSS builds (insiders versions might be, though – see https://github.com/microsoft/vscode-remote-release/issues/574). Perhaps we could look into making an open source replacement of our own, based on the stubs that _are_ provided in the source code?
I would love to see this as my current company does not approve the pre-built binaries from MS so we all use VSCodium and would love to use Remote extension functionality.
Yeah that would be super cool. I don't have the capacity to contribute to that currently, but would help out where possible.
If insiders currently supports unlicensed builds, it may mean that the standard version will support them in the near future; also a hope is to get VSCodium automated builds of the insider's version in the near future (#148). That would potentially unblock using the remote extensions without a big effort building from piecemeal.
hello, any news on this? I love vscodium as is, but I would like to use this as well
In the meantime, ponyssh has done what I needed
@kmantel
In the meantime, ponyssh has done what I needed
Yeah that might be cool, but we'd still prefer the actual remote development extensions.
Any news here?
@sarpik Pony SSH could be a good start though? :thinking:
Pony SSH asks my remote server SSH password even i loaded it to agent, so, looks like insecure( I really want use SSH remote development
any news of remote access to the remote-ssh ?
I am interested in contributing my time to create an ssh extension. If anybody has any pointers as to where I should start, they are very welcome.
My initial understanding is that I will need to figure out how to start vscode headless to use it for the "server" and develop an extension which will register different providers remotely.
For future readers
Please, avoid any news? comments. You are just pinging everybody in this thread for no reason. It is likely that people will get annoyed and unsubscribe, so even if there will be news they won't update this issue.
I was looking for a solution to this and found something on the way but I'm not certain about it.
Can anyone tell me if it's a good idea to use sshfs in order to mount the remote server into the local working directory and then use VSCodium to browse/edit the files ?
It seems like it's too good to be true, why would one need any extension then ?
@Lcchy Mainly for the debugger I think. Other things (version control and code jump to dependencies) most of the time work fine with just files, but debugging requires running a special process on the server (for some languages it's a separate script, e. g. debugpy for Python, for others it's just a runtime option, e. g. node --inspect) and port forwarding (so that nobody else can “debug” your code :) to work.
Most helpful comment
I am interested in contributing my time to create an ssh extension. If anybody has any pointers as to where I should start, they are very welcome.
My initial understanding is that I will need to figure out how to start vscode headless to use it for the "server" and develop an extension which will register different providers remotely.
For future readers
Please, avoid
any news?comments. You are just pinging everybody in this thread for no reason. It is likely that people will get annoyed and unsubscribe, so even if there will be news they won't update this issue.