-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move directory with installed Che JS Plugin from the WS Master instance to the separate service #8221
Comments
I thought, the configuration of the plugins of a workspace would be part of the description of the workspace itself. Why would we make a service to know the installed plugins? |
Yes plugins will be part of the description of the workspace, in this case as you understand we can't keep IDE with plugins on the WS master, because the plugin list will be workspace specific. |
There is probably two level of configuration that we need to configure:
Are you considering those two aspects? |
Could you please clarify a bit what this means:
What do you mean by "dedicated server" and "plugins scripts" ? |
System level is something new for me and I don't understand why we need this feature. |
@vparfonov As a user of Che. If you are interested by a plugin which gives you a Git plugin. Do you want to go into the configuration of each workspaces, and for each workspace enable the Git Plugin? And then similarly, when you'll create a new workspace, you'll have to again go add that plugin? As a user, I should be able to configure certain plugins for all my workspaces. |
@slemeur As a user how many workspace do you have plan create per day? |
It depends how Che is integrated with your Devops toolsuite. Certain integrations will lead users to get one workspace created per work item. (see JIRA plugins and integration in OSIO) |
Description
Need to move directory with installed Che JS Plugin from the Workspace Master instance to the separate service. This make customization model more flexible.
Here we will provide special service that will be part of workspace and have ability provide information about installed plugins and plugin content itself
The text was updated successfully, but these errors were encountered: