e0890235fa
* Support identity provider token retrieval in both JSON or URL formats. That's required because some identity providers (such a `openshift-v3`) correctly return the token information in JSON, as expected. So switching to the url-based syntax should only used when the returned json is invalid. Signed-off-by: David Festal <dfestal@redhat.com> * Introduce an `OpenShiftClientConfigFactory` to allow customizing the OpenShift config returned according to the current context (workspace ID, current user) Signed-off-by: David Festal <dfestal@redhat.com> * Openshift Infra + Multi-user => allow using OpenShift identity provider to connect to openshift with the OS oauth token of the current Che user. This introduces a new property: `che.infra.openshift.oauth_identity_provider` Signed-off-by: David Festal <dfestal@redhat.com> * Notify the user when a workspace cannot be started from the nav bar. Signed-off-by: David Festal <dfestal@redhat.com> * Add the ability to install the Openshift certificate into Keycloak Signed-off-by: David Festal <dfestal@redhat.com> * Add a yaml file to provide the openshift certificate as a secret, in case it has to be installed into the dedicated Keycloak server. Then the commands to install Che multiuser on Minishift with this certificate are: ``` oc new-project che oc process -f multi/openshift-certificate-secret.yaml -p CERTIFICATE="$(minishift ssh docker exec origin /bin/cat ./openshift.local.config/master/ca.crt)" | oc apply -f -; \ oc new-app -f multi/postgres-template.yaml; \ oc new-app -f multi/keycloak-template.yaml -p ROUTING_SUFFIX=$(minishift ip).nip.io; \ oc apply -f pvc/che-server-pvc.yaml; \ oc new-app -f che-server-template.yaml -p ROUTING_SUFFIX=$(minishift ip).nip.io -p CHE_MULTIUSER=true -p CHE_INFRA_OPENSHIFT_OAUTH__IDENTITY__PROVIDER=openshift-v3; \ oc set volume dc/che --add -m /data --name=che-data-volume --claim-name=che-data-volume ``` Of course it's still needed to register the `openshift-v3` identity provider in the Keycloak server, as well as, add the corresponding `OAuthClient` object in Minihshift. Signed-off-by: David Festal <dfestal@redhat.com> |
||
|---|---|---|
| .. | ||
| action | ||
| base | ||
| bats | ||
| che | ||
| cli | ||
| dev | ||
| dir | ||
| init | ||
| ip | ||
| keycloak | ||
| lib | ||
| mount | ||
| postgres | ||
| test | ||
| theia | ||
| README.md | ||
| build.include | ||
| build.sh | ||
README.md
Eclipse Che - Dockerfiles
This che-dockerfiles repository is where all dockerfiles for Che Launcher, Che's CLI and Che's Stacks are hosted.
Eclipse Che
https://www.eclipse.org/che/. Next-generation Eclipse platform, developer workspace server and cloud IDE. Che defines workspaces that include their dependencies including embedded containerized runtimes, Web IDE, and project code. This makes workspaces distributed, collaborative, and portable to run anywhere on a desktop or a server ... Read More
Getting Started
You can run Che in the public cloud, a private cloud, or install it on any OS. Che has been tested on Ubuntu, Linux, MacOS and Windows. The step by step guide will get you going.
The che repository is where we do development and there are many ways you can participate, for example:
- Submit bugs and feature requests and help us verify them
- Review source code changes
- Improve docs
Customizing
There are many ways to customize Che out-of-the-box including stacks, templates, commands, IDE extensions, server-side extensions plugins, assemblies, RESTful APIs, and editors.
Contributing
If you are interested in fixing issues and contributing directly to the code base, please see How to Contribute. It covers:
Feedback
- Support: You can ask questions, report bugs, and request features using GitHub issues.
- Roadmap: We maintain the roadmap on the wiki.
- Weekly Meetings: Join us on a hangout.
License
Che is open sourced under the Eclipse Public License 1.0.