Configure CodeTogether on-premise server as custom plugin repository in IDEs

[oschlueter]

Is your feature request related to a problem? Please describe. All users of the on-premise version have to download the correct plugin version from the on-premise server and install it manually to ensure that the plugin version matches the server version. This manual effort has to be repeated each time the on-premise server is updated. Using an IDEs marketplace to install the plugin will use the latest release of the plugin which might differ from the CodeTogether version deployed on-premise.

Describe the solution you'd like I want to configure the on-premise server as a custom plugin repository and use it to install the plugin without "manual effort", i.e. downloading the plugin and installing it from disk. I want to update the plugin via the IDE whenever the on-premise server is updated.

Additional context

• Eclipse and JetBrains IDEs support custom plugin repositories but VS Code does not (see here).
• This feature request is already supported for Eclipse (see https://$SERVER/clients/).

[toddewilliams]

I really like this idea and what it seeks to accomplish, but I'd like to try to see if simplifying the implementation suggestion would be acceptable.

What if the plugin/extension updates to an existing installation could be done automatically from the server (even be pushed when required), but the first install was still manual. Does that solve enough of the issue?

[oschlueter]

Thanks! Yes, I do think that reducing a recurring manual effort to a one-time manual effort would be a great improvement.

[GenuitecKanbot]

Happy to report this issue is resolved! (from Kanbanbot)