@silverhikari : yes, it worked (as expected). But, why change "serverApplicationName" to code-server in the first place? What is the reason behind that since the original remote-ssh extension by microsoft seems to be not working at all on vscodium, even patched ? Well, at least, it is something written on the vscodium github wiki, not sure if with some more hack, that i am not aware of, you can use the ms' remote-ssh.
ms' remote-ssh extension downloads an archive on the remote machine whose url is based on a commit hash that it gets from local code's product.json. obviously it fails when the extension is on host's vscodium with untouched product.json:"commit".
Something like https://update.code.visualstudio.com/commit:%{COMMIT_HASH}/server-linux-x64/stable
to get vscode-server-linux-x64.tar.gz
I've tried to put on my vscodium's product.json:
"nameShort": "Code",
"nameLong": "Visual Studio Code",
"commit": "eaa41d57266683296de7d118f574d0c2652e1fc4",
with that commit taken from vanilla code installation but no luck in using vscodium + ms's remote-ssh.
it give me [<unknown>][c721d762] Unauthorized client refused.
Back to the question: what is the purpose of changing "serverApplicationName" to "code-server" if ms' remote-ssh doesnt want to run here at all?
Gonna try code-features' patch.json when i will get some spare time.
Pinned Comments
silverhikari commented on 2023-01-28 15:24 (UTC) (edited on 2023-01-28 18:50 (UTC) by silverhikari)
if you are having problems with the installation step with it giving a decoder error, you need to uninstall and reinstall vscodium-bin and vscodium-bin-marketplace. then try to install this package again.