-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Closed
Labels
kind/enhancementA feature request - must adhere to the feature request template.A feature request - must adhere to the feature request template.severity/blockerCauses system to crash and be non-recoverable or prevents Che developers from working on Che code.Causes system to crash and be non-recoverable or prevents Che developers from working on Che code.status/in-progressThis issue has been taken by an engineer and is under active development.This issue has been taken by an engineer and is under active development.
Milestone
Description
Description
Currently a Che stack (i.e. java-maven) is associated to one or more samples (e.g. web-java-petclinic and console-java-simple). But often different samples of the same stack requires different settings (env variables, memory, commands) and making generic stacks that work with every project is hard.
Another point is that from a UX point of view it's more straightforward to select a vue.js or a angular stack rather than selecting the node js stack and then the angular sample.
So this issue is about the proposal to associate every stack to one unique project sample. The project, as well as the commands, would be specified in the the stack devfiles. The user would still be able to override the sample stack project and commands.
Metadata
Metadata
Assignees
Labels
kind/enhancementA feature request - must adhere to the feature request template.A feature request - must adhere to the feature request template.severity/blockerCauses system to crash and be non-recoverable or prevents Che developers from working on Che code.Causes system to crash and be non-recoverable or prevents Che developers from working on Che code.status/in-progressThis issue has been taken by an engineer and is under active development.This issue has been taken by an engineer and is under active development.
