Computing : VisualStudioCode remote sessions on Workgroup Server

Adapted from Tadej's ATLAS documentation https://atlassoftwaredocs.web.cern.ch/guides/vscode/ssh/#hosts-with-home-folder-on-network-storage

Issue

VSCode does not work well with remote network storages, that use tickets/tokens for access. I.e., Like running VSCode on a desktop machine with a remote ssh install on a workgroup server. The ordinary HOME paths are on AFS as file system and the access token has to be renewed on a daily base. Unfortunately, VSCode is unaware of such details and so a remote install will loose its access to the file system and end up in a error state consuming significant CPU.

Solution

Configure VSCOde to use only explicitly local paths on the remote machine for persistent ssh installations like

{
    "remote.SSH.lockfilesInTmp": true,
    "remote.SSH.serverInstallPath": {
        "naf-dev~alma9": "/var/tmp/foo/vscode/alma9",
        "naf-dev~centos7": "/var/tmp/foo/vscode/centos7",
        "naf-dev": "/var/tmp/foo/vscode/default",
    }
}

Paths on DUST might also work, since access control is per username - but as DUST is a network file system, performance could degrate.