Self Hosting for Che

[gorkem]

Description

We need to enable self hosting of Che for the purpose of developing Che. On self hosting, Che should be able to run projects that exists on the workspace as a replacement or addition to create and start a second hosted instance that is based on the basic Che.

I think this will require a slightly different approach to self hosting for different parts of Che. IMHO the priority of those are 1.) Anything on workspace 2.) IDE 3.) Che server (wsmaster).

[gorkem]

Talked with @skabashnyuk and he mentioned an oldish idea about running a second wsmaster on the workspace and starting a second IDE instance that uses the hosted wsmaster. This will require us to be able to tell IDE to use a different wsmaster ws-agent. @vparfonov any ideas?

[skabashnyuk]

this will require us to be able to tell IDE to use a different wsmaster

This will require us to be able to tell IDE to use a different ws-agent

[gorkem]

@skabashnyuk correct, should be ws-agent. Must be the Fridays.

[benoitf]

Does this "new instance of ws-agent" will have tomcat development mode turned on as well ? by using exploded war files archives so classloader/war is restarted if a jar file in its dependencies are updated ?

[skabashnyuk]

Maybe. For the start, it would be nice to see it working somehow.
Now I'm working on prototype when plugin touches only ide side. It's a bit simpler use case
because we can reuse original ws-agent.

[skabashnyuk]

@gorkem 1 an 2. we have right now. Do you want to keep this epic for self-hosting of wsmaster?

[gorkem]

I am under the impression that wsmaster is not something that only vendors would be interested to extend. So even if we keep this issue for it. I do not see it getting a lot of love.

[skabashnyuk]

Can you explain what is left to do here?

[skabashnyuk]

@gorkem would you like to keep this issue?

[gorkem]

We can close it, we are handling this already