search

jeanp413 / open-remote-ssh

VSCode Remote Development: Open any folder on a remote machine using SSH.
MIT License
294 stars 40 forks source link

FR: export/import for known remote workspaces in Remote Explorer #47

Open GitMensch opened 1 year ago

GitMensch commented 1 year ago

Hostnames are in .ssh/config starting a workspace adds it to the remote explorer list - I'd like to distribute those to others, what do I need to copy?

jeanp413 commented 1 year ago

You mean the child entries (folders) for each hostname entry? those are stored internally by vscode using the globalState api, not possible to copy them

GitMensch commented 1 year ago

You mean the child entries (folders) for each hostname entry?

Yes.

Those are stored internally by vscode using the globalState api, not possible to copy them

Hm, so that's a FR now to add import/export functionality for them :-)

GitMensch commented 1 year ago

I'm trying to get user-acceptance for using remote workspaces and somehow those users don't want to connect to each machine (the list of machines and general configuration is now shared with an initial ssh config file) and open each workspace that exists there by hand once.

As the extension already reads the ssh config - wouldn't it be possible to add "magic/tagged comments" in there that specify a list of remote workspaces that should be shown?

ecxod commented 2 months ago

You mean the child entries (folders) for each hostname entry? those are stored internally by vscode using the globalState api, not possible to copy them

The Idea is that now there are a lot of Flavors of VSC, and every day there is one that dies and one that is born, and it is becoming more important to be able to migrate from one installation to another. I personally created a habit to store the workspace file in the same place on all servers But a export/import function is very necessary. The globalstate API should be no impediment to make such a function.