-
Notifications
You must be signed in to change notification settings - Fork 114
Add realworld go sample #96
Conversation
Signed-off-by: Anatoliy Bazko <[email protected]>
Signed-off-by: Anatoliy Bazko <[email protected]>
Signed-off-by: Anatoliy Bazko <[email protected]>
Signed-off-by: Anatoliy Bazko <[email protected]>
I've added |
devfiles/go/devfile.yaml
Outdated
@@ -18,7 +18,7 @@ components: | |||
- | |||
type: dockerimage | |||
# this version is used in the plugin | |||
image: quay.io/eclipse/che-golang-1.10:nightly | |||
image: quay.io/eclipse/che-golang-1.12:nightly |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we need to support the go 1.10 stuff too? or just drop it in favour of the latest?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see also eclipse-che/che-plugin-registry#224
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nickboldt @amisevsk
I have no idea
I would say let's keep it for a while, is it ok?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm currently looking to deprecate 1.10 if possible, so if the devfiles work with 1.12, that makes my life easier.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm generally against adding pure backend samples to the devfiles registry as they provide a rather poor user experience (see the nodejs-mongo sample we're currently working on fixing).
devfiles/go-web-sample/devfile.yaml
Outdated
memoryLimit: 512Mi | ||
- | ||
type: dockerimage | ||
# this version is used in the plugin |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This comment is a worry; if the che plugin has latest
version, will this devfile stop working when the plugin is eventually updated to use a later version?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think so.
Signed-off-by: Anatoliy Bazko <[email protected]>
It was decided here eclipse-che/che#13529 |
AFAICT the work that was done was very important for running Go on Che in the general case (if you're referring to issue eclipse-che/che#13803), so the work is not for nothing. The issue I have with applications that are only backend with no frontend is that we run into eclipse-che/che#14392 (which runs the same realworld backend app). |
I observed several issues:
|
Signed-off-by: Anatoliy Bazko <[email protected]>
Signed-off-by: Anatoliy Bazko <[email protected]>
Signed-off-by: Anatoliy Bazko <[email protected]>
@amisevsk |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested and devfile works with a few caveats below.
Additionally: the golang plugin seems to be unable to handle methods on structs that are defined in other files (see article.go
, which defines methods on handler
). This is not an issue for this PR, though.
Finally, the project used in this devfile does not have a LICENSE file (like most realworld samples) and so will come with the same issues in redistribution: eclipse-che/che#14790
Signed-off-by: Anatoliy Bazko <[email protected]>
Actually it works. The trick is to set the project as a workspace root. But there is no way to do it automatically, that's way this issue became important eclipse-che/che#13080 |
@amisevsk |
@tolusha any reason we're using the the version from "xesina" instead of the version it was forked from (which is MIT licensed)? |
Strictly speaking, no we don't: we're not distributing the sample, just pointing to some code on github. However, if we want to distribute the sample (in a airgapped version of CRW), we'll have to have the licensing in order. |
Which one? Probably I am not aware of. |
The repo is a github fork of another github project (which has a license) |
see comment eclipse-che/che#13803 (comment) |
Signed-off-by: Valeriy Svydenko <[email protected]>
Signed-off-by: Anatoliy Bazko [email protected]
What does this PR do?
It adds real-world-go-sample
https://github.com/xesina/golang-echo-realworld-example-app
What issues does this PR fix or reference?
eclipse-che/che#13803
Related PRs
eclipse-che/che-plugin-registry#224
eclipse-che/che-theia#443
How to test
->
docker.io/eclipse/che-remote-plugin-go-1.12.9:next
(see Update go version to 1.12.9 che-theia#443)or retag it from
docker.io/abazko/che-remote-plugin-go-1.12.9:next