Closed l0rd closed 4 years ago
cc @slemeur
Updated with a more complete list to be targeted for GA
@l0rd @slemeur no PHP stacks?
@l0rd how can we have a camel stack if we don't have a camel plugin yet?
About quarkus: if we are talking about building native programs, the target would be any image that has the necessary libraries. In the end, there is no "server" to be installed.
Che server dev stack needs Golang, no?
@l0rd how can we have a camel stack if we don't have a camel plugin yet?
A copy/paste issue. Fixed now. Thanks
About quarkus: if we are talking about building native programs, the target would be any image that has the necessary libraries. In the end, there is no "server" to be installed.
Agree. I was thinking about an image where the quickstart sample was pre-built so that the developer can get started quickly.
Che server dev stack needs Golang, no?
I don't think so. I think Golang was only used for the exec agent but in Che 7 that's a separate plugin.
@l0rd + @tsmaeder : Added PHP.
So will we SUPPORT all these stacks, or will only a subset of these be Red Hat GA-level supported? Right now for CRW 1.x / Che 6 we only support Node8 and Java8, with the rest being community-supported. I've opened https://issues.jboss.org/browse/CRW-225 to track the downstream specs.
Che server dev stack needs Golang, no?
I don't think so. I think Golang was only used for the exec agent but in Che 7 that's a separate plugin."
Not sure if it's relevant but the Che 6 operator (and the CRW 1.x operator) both rely on golang too:
https://github.com/eclipse/che-operator/blob/master/Dockerfile#L13
@nickboldt good point. I have added a Che operator stack, it should not be part of the che-server stack though.
@l0rd @slemeur golang chag example is broken, see https://github.com/eclipse/che/pull/13176. Ok to strike that one?
@tsmaeder +1
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.
Description
For Che 7 we want to release some new stacks that use the new ws.next based model and theia as editor.
Stacks guidelines
"sidecar.org.eclipse.che.editor.theia.memory_limit": "512Mi"
)"sidecar.org.eclipse.che.vscode-redhat.java.memory_limit": "1024Mi"
"memoryLimitBytes": "512000000"
.next
HOME=/home/user
: arbitrary users don't have a home folder defined in/etc/passwd
hence we should define one and the convention is to set it to/home/user
mvn
) need to access the folder a trick is to mount the folder as a volume:PS1
environment variable${current.project.path}
): use environment variables instead and use the sample folder. For example:cd ${PROJECTS_PATH}/java-web-simple
.Current issues
Stacks list
Java
maven
andpostgres
images as runtime and Java LS) @l0rdNodeJS
Python
.NET Core
Go
PHP
Che Development
Other misc