Skip to content
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

Fix samples endpoint issues #13964

Closed
2 tasks
l0rd opened this issue Jul 23, 2019 · 6 comments
Closed
2 tasks

Fix samples endpoint issues #13964

l0rd opened this issue Jul 23, 2019 · 6 comments
Labels
kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system.
Milestone

Comments

@l0rd
Copy link
Contributor

l0rd commented Jul 23, 2019

Is your enhancement related to a problem? Please describe

For some of the samples projects in the devfile registry, the preview URL proposed by Theia port plugin is not the correct application URL. Even if the workspace sample starts properly users won't be able to open the application in the preview panel. That's definitely a bad UX.

Describe the solution you'd like

The short term solution is to:

  • identify the samples that have this problem
  • fix the samples (and fork them if needed)

The long term solution is to add a new previewURL attribute to the devfiles commands #13945

@l0rd l0rd added the kind/enhancement A feature request - must adhere to the feature request template. label Jul 23, 2019
@ibuziuk
Copy link
Member

ibuziuk commented Jul 23, 2019

@l0rd if you do not mind I will put this issue to the End Game Plan as a subtask for Need to make sure that all devfiles from registry work on che.openshift.io

@l0rd
Copy link
Contributor Author

l0rd commented Jul 23, 2019

@ibuziuk of course that's perfect.

One thing though: this can also be a multi-team effort as it has been the case for #13529 (comment). You coordinate that but others teams can help as well. I think it worked pretty well for #13529

@l0rd l0rd added the severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. label Jul 24, 2019
@l0rd l0rd added this to the 7.0.0 milestone Jul 24, 2019
@l0rd l0rd added severity/P1 Has a major impact to usage or development of the system. and removed severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. labels Jul 24, 2019
@amisevsk
Copy link
Contributor

From what I've seen, the current endpoint issues are:

  • NodeJS + Mongo is a backend app, hard to interact with in browser: nodejs-mongo devfile sample issues #14009
    • e.g. navigating to /api/user requires an authorization token
  • PHP-MySQL: Application serves app at /crud-php/public, opening the endpoint (to /) gives just a directory structure
  • PHP Simple: Same as above; opens to "Index of /" page. Need to navigate to /php-web-simple to get actual app.

@amisevsk
Copy link
Contributor

amisevsk commented Aug 9, 2019

I've opened PR eclipse-che/che-devfile-registry#77 to work around the php devfile issues. The NodeJS + Mongo devfile is (I think) just a bad sample application; it's hard to interact with a REST backend from the browser.

@ibuziuk
Copy link
Member

ibuziuk commented Aug 13, 2019

@slemeur @l0rd, in general, I believe we need to reconsider the samples we are using and get rid of / deprecate https://github.com/che-samples . IMO we should use vendor samples for all the devfiles like https://github.com/spring-projects/spring-petclinic

@slemeur slemeur modified the milestones: 7.0.0, 7.1.0 Aug 21, 2019
@ibuziuk
Copy link
Member

ibuziuk commented Aug 29, 2019

Closing:

  • preview url should be soon supported in devfile
  • samples should be k8s based samples (samples should be kube-native for Eclipse Che )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

4 participants