How to use this with SSH remote

Question

How to use this with SSH remote

GitMensch opened this issue 10 months ago · 15 comments

Or: Do you plan to add REH binaries?

Answer 1 · 2024-03-06T01:44:20.000Z

@GitMensch Actually, everytime I build, it makes reh archives. I didn't think anyone wanted or used it, because isn't that just the web version of VSCode? Because in that case there's really no point, and Codium doesn't offer any benefit over upstream. Codium is for people who want compiler optimization, to use it on old OSes i.e. windows 7, or because they dislike the vscodium logo.

Answer 2 · 2024-03-06T05:06:54.000Z

No, the REH version is needed for using SSH (or is version WSL) remote. For this the communication goes to a server with the same hash number, which is different for Codium.

Answer 3 · 2024-03-07T23:38:44.000Z

@GitMensch OOOO ok. I will release the reh archives alongside them from now on. Thnx. Sorry I didn't before, I could have the whole time because it builds it as part of the whole compilation process, I just didn't think it was necessary. I never use the web version, ssh, or the tunnel introduced recently, so I didn't know anything about it.

Answer 4 · 2024-03-15T07:40:37.000Z

@GitMensch Latest 1.87.2 version has REH for Linux and Windows > https://github.com/Alex313031/codium/releases/tag/1.87.2.24075

Answer 5 · 2024-03-15T08:54:11.000Z

Than you. The codium_reh works on my boxes; to have that automatically installed by Open SSH Remote one can configure (=override) its setting remote.SSH.serverDownloadUrlTemplate
https://github.com/jeanp413/open-remote-ssh/blob/8191939de706952fa035f80a6fce0e85f85495f6/package.json#L81

But the installation would have to be done manually for now, as its install script expects it to have in gzip'd tar format, not as zip file https://github.com/jeanp413/open-remote-ssh/blob/8191939de706952fa035f80a6fce0e85f85495f6/src/serverSetup.ts#L318-L343

To ease that and allow automatic installation - can you please adjust the reh binaries to be made available as tar.gz?

Answer 6 · 2024-03-15T08:57:56.000Z

Jut out of interest: your binaries include node 16.17.1; is there a plan to increase that or is that version necesary to support older environments?

Answer 7 · 2024-03-16T14:39:40.000Z

@GitMensch Yeah, next release I can leave them as .tar.gz

And well, as you know this fork is using Node 16 and Electron 22 for old OS support, i.e. Windows 7/8/8.1 & Ubuntu 18.04/Debian 9. But actually, VSCodium is also using Node16 (only for the REH archives), see > https://github.com/VSCodium/vscodium/blob/master/patches/linux/reh-node16.patch

Answer 8 · 2024-05-12T03:28:23.000Z

@GitMensch How are the reh archives working for you now? I am making Linux and Windows ones, using Node 16 (same node as the Electron 22.3.27 that this fork is using)

Answer 9 · 2024-05-12T12:38:29.000Z

I've tested them directly after your last update and they worked fine, only the naming schema difference to VSCodium reh binaries was creating extra effort to get the automated download working (I've opted for a manual download back then instead). If not adjusted so far I'd suggest to use the schema from VSCodium. In any case this issue should be closed-fixed.