How can I use a remote workspace storage directory ?

[fungiboletus]

Hei, since the version 2.2.0 and #13 I don't manage to use a workspace storage directory on my remote vscode. I prefer to have it remotely rather than locally because I switch between a few computers and I don't want to synchronise the workspace storage directory.

I reverted to the version 2.1.0 but I would like to know if this kind of feature is supposed to work, and if you would accept a pull request to support local storage directory and remote storage directory.

And thanks for your work, this extension is appreciated 🙂

[betterthanclay]

I'm looking for a solution here too - unfortunately it seems that 2.2.0 has broken the previously working behaviour where remote workspace files hosted on the remote server would be loaded from the path in the remote server's settings file.

Now, I'm just getting an empty workspaces pane when on the remote, regardless it seems of config changes and uninstalling the extension on the remote host… unless I'm missing something?

And yes, thank you for your work, this is a great extension 👍

[sirfuzzalot]

@fungiboletus @betterthanclay I've been trying to find a way to easily support this remote workflow again without rolling back the benefits I think 2.2.0 brings to devs storing their local and remote workspaces both locally. I attempted to add a Run Extension in Remote Host Only option to Workspace Explorer's configs, but unfortunately VSCode does not let Workspace Explorer programmatically write this specific value (see below) into the global configs via the WorkspaceConfiguration API.

{
  "remote.extensionKind": {
    "tomsaunders-code.workspace-explorer": ["workspace"]
  },

  "your-other-configs": "and-their-values",
}

Give it a try with your setup by adding it to your settings.json file. I was able to get this to work using the Remote WSL extension.

[fungiboletus]

Hei,

I confirm that adding the following configuration in my settings.json file provides the behaviour I want using version 2.2.0 🙂 Thanks !

"remote.extensionKind": {
  "tomsaunders-code.workspace-explorer": ["workspace"]
},

[betterthanclay]

Yeah, that's working for me - shame it can't be included as a managed config parameter, but I can set it and forget it.

It might be worth including some instructions in a notice in the config window (if possible), or at least in the readme as I think others will be using the extension this way round.

Thanks for looking into it!