So to recap from what i am getting from your issue
you want to use the extensions on the REMOTE, and not sync the ones on the Client?
I mean this in theory would be easyish to implement, just adding a flag,
Side nore, for future issues, i would reccomend explaining how you would want it to work so that we can understand more
The title of a issue is a summary,
And SSHCODE works by using ssh to run commands on the REMOTE, which it downloads a custom version of cdr/code-server and runs it, before Proxying the port that code-server is running on, back to local host.
In theory it would be possible to use the REMOTES local extensions/settings,
That's correct. The issue is that some organisations have private plugins for internal systems that aren't installed, or allowed to be installed on laptops (nor would they work: they depend on software only installed on the desktops). It would be great to be able to use them through this tool.
Well, Most of your private plugins should work just fine if you make it use vscode-datadir
Specific Microsoft plugins such as the Remote toolset will not work at all, as they are hardcoded to only work with official microsoft releases,
If the private plugins are not hardcoded to only work with a specific setup, then yeah they should work, i would recommend forking this and adding the feature as a flag for you,
Currently im waiting on my fork to be added into the repo to make the tool work on windows.
On Tue, Jan 21, 2020 at 11:50 PM Merith ***@***.***> wrote:
A workaround you could do to make it work, is to make symlinks from the
VSCode data dir to the sshcode-server datadir,
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#164>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABF2IK7V7SBNAE6MYCR3YITQ6532JANCNFSM4KJSABSQ>
.
So that you can use manual extensions on the remote host