this quick patch should fix the problem che-incubator/che-code#248
but need to test more thoroughly + adapt to a custom OpenVSX

My quick patch to set the resourceUrlTemplate fixes the [error] Error: No extension gallery service configured.
But the requested URL is incorrect.

2023-06-28 17:34:45.715 [info] Installing extension: vscodevim.vim
2023-06-28 17:34:46.130 [info] Request to 'https://che-dogfooding.apps.che-dev.x6e0.p1.openshiftapps.com/oss-dev/web-extension-resource/open-vsx.org/vscode/unpkg/vscodevim/vim/1.25.2/extension' failed with status code 404
2023-06-28 17:34:46.130 [warning] Error while fetching extension resources list Not Found

Needs more investigation.

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

/remove-lifecycle stale

One more example of the extension reporting the same error
https://marketplace.visualstudio.com/items?itemName=k--kato.intellij-idea-keybindings

I found out how to install such kinds of web (UI) extensions like https://open-vsx.org/extension/vscodevim/vim or https://open-vsx.org/extension/k--kato/intellij-idea-keybindings

There's a Remote: Extension Kind setting in Che-Code.

It allows to override where an extension should be run.

Adding the following section to the settings.json file

"remote.extensionKind": {
        "k--kato.intellij-idea-keybindings": [
            "workspace"
        ],
        "vscodevim.vim": [
            "workspace"
        ]
    }

allowed me to install both mentioned extensions.

@azatsarynnyy that's amazing, I'm glad to hear there's finally a workaround for this 😁

It's a shame that you have to manually specify which web-extensions you want to allow to be installed locally -- would be nice if there was a way for us to force all web-extensions to be installed in the workspace with a setting the in remote settings.json.

Still, a workaround is a huge improvement here :D