On handling raw devfile urls, request content by the url, and check if the content is a devfile. If yes treat the url as a raw devfile url. --------- Signed-off-by: ivinokur <ivinokur@redhat.com> Co-authored-by: Anatolii Bazko <abazko@redhat.com> |
||
|---|---|---|
| .ci/openshift-ci | ||
| .github | ||
| .mvn | ||
| .vscode | ||
| assembly | ||
| build | ||
| core | ||
| deploy/cert-manager | ||
| docs | ||
| infrastructures | ||
| multiuser | ||
| typescript-dto | ||
| wsmaster | ||
| .gitattributes | ||
| .gitignore | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| NUMBERING.md | ||
| README.md | ||
| RELEASE.md | ||
| check_properties_description.sh | ||
| devfile.yaml | ||
| make-release.sh | ||
| pom.xml | ||
README.md
What is Che server
Che Server provides an API for managing Kubernetes namespaces and to retrieve devfile content from repositories, hosted on GitHub, GitLab, Bitbucket and Microsoft Azure Repos.
Project structure
Che Server is mostly a Java web application deployed on an Apache Tomcat server in a container. Che Server uses the following modules:
OAuth1 / OAuth2 API implementations
- wsmaster/che-core-api-auth
- wsmaster/che-core-api-azure-devops
- wsmaster/che-core-api-bitbucket
- wsmaster/che-core-api-github
- wsmaster/che-core-api-gitlab
Factory flow implementations
- wsmaster/che-core-api-factory-azure-devops
- wsmaster/che-core-api-factory-bitbucket
- wsmaster/che-core-api-factory-bitbucket-server
- wsmaster/che-core-api-factory-github
- wsmaster/che-core-api-factory-gitlab
- wsmaster/che-core-api-factory-shared
Kubernetes namespace provisioning
- infrastructures/kubernetes
- infrastructure/openshift
- infrastructures/infrastructure-factory
Other modules are deprecated and will be removed in the future.
License
Join the community
The Eclipse Che community is globally reachable through public chat rooms, mailing list and weekly calls. See the Eclipse Che Documentation about how you can join our community.