Shulou(Shulou.com)06/02 Report--

This article mainly explains "the detailed introduction of Eclipse Che 7", interested friends may wish to have a look. The method introduced in this paper is simple, fast and practical. Let's let the editor take you to learn the detailed introduction of Eclipse Che 7.

Introduction to Eclipse Che

EclipseChe is a Kubernetes- native IDE and developer collaboration platform. As an open source project, the core goal of EclipseChe is to accelerate the entry of projects and developers: as a zero-installation development environment running in a browser, EclipseChe makes it easy for anyone to join your team and contribute to the project. Eliminate inconsistencies between developer environments: no longer: "but it works on my machine." In everyone's environment, your code works exactly the same way. Provide built-in security and enterprise readiness: as EclipseChe becomes a viable alternative to the VDI solution, it must be secure and must support enterprise requirements, such as role-based access control and the ability to remove all source code from the developer's machine. To achieve these core goals, EclipseChe provides: workspaces: container-based developer workspaces that provide all the tools and dependencies needed to write, build, test, run, and debug applications. Browser-based IDE: bundles browser-based IDE with language tools, debuggers, terminals, VCS integration, etc. Extensible platform: bring your own IDE. Define, configure, and extend the tools required for your application by using plug-ins that are compatible with VisualStudio code extensions. Enterprise integration: multi-user capabilities, including Keycloak for authentication and integration with LDAP or AD.

It provides:

A centralized development environment running on Kubernetes multi-container workspaces

Each developer can copy through the EclipseChe factory pre-built stack with just one click.

You can create a custom stack for any language or runtime enterprise integration through Keycloak through IDE based on AD/LDAP browsers

Integrate with Che-Theia or any other Web IDE (such as Jupyter)

Support for the latest tool protocol: Language Server Protocol,Debug Adapter Protocol

Plug-in-in mechanism, compatible with VisualStudio code extensions

SDK is used to create a custom cloud development platform

Start using EclipseChe

Follow the Quick start guidelines for installing EclipseChe locally on your computer

Learn more about EclipseChe: EclipseChe and architecture overview

Discover EclipseChe featur

If you are interested in joining the community

Join us through the following channels: public chat: join the public EclipseCheMatterest channel to chat with developers. GitHub project repository: reports bug, requests features, and contributes to the main EclipseChe repository. Improve documents in the EclipseChe document repository. Support: visit StackOverflow to help other users of EclipseChe: EclipseChe on StackOverflow. Community blogs: learn about the latest developments in EclipseChe and submit your blog posts to the EclipseChe blog. Biweekly meeting: join our community meeting every other Monday. Roadmap: see the development roadmap on wiki.

Workspace model

Che defines workspaces as project code files and all the dependencies needed to edit, build, run, and debug them. Che treats IDE and the development runtime as workspace dependencies. These items are embedded and are always included in the workspace. This is different from the classic workspace definition, which may include project code, but requires developers to bind their IDE to their workstations and use it to provide runtime locally. Workspaces are isolated from each other and are responsible for managing the life cycle of their components. Developers using EclipseChe use their containers directly in their developer workspaces. The CHE workspace is the Kubernetes pod that allows you to copy the application runtime (and its micro services) used in production and provide a "dev mode" layer on top of it, adding IntelliSense and IDE tools.

Browser-based IDE

EclipseChe provides browser-based IDE for its workspace. The default IDE is built on Theia and has the following functions: Monaco-based editor: quick response editor: CodeLens language server protocol: language tools debugging adapter protocol: debugger tools command debugger: support everything from keyboard tasks: extend tasks in VisualStudio code and support Che commands embedded preview: preview applications directly from IDE Includes Markdown preview customizable layout: use drag and drop and more: outline view, search, Git

Different IDE for different use cases in Eclipse Che

IDE is completely decoupled, so different IDE can be inserted into the Che workspace: it can be based on Eclipse Theia (because it is the framework for building Web IDE), such as Sirius: it can be a completely different solution, such as Jupiter or Eclipse diritable: it can be a completely different solution for use cases where the default IDE does not cover users or where a dedicated tool is used instead of IDE.

Extensible platform

EclipseCe is a good platform for building cloud-native tools, providing contributors with a powerful extensibility model with enjoyable development experience. Eclipse Che can be extended in different ways:

Plug-in to add functionality to IDE. The Che-Theia plug-in relies on API, which is compatible with Visual Studio code. The plug-in is isolated and provides its own dependencies in the container.

Stack to create a preconfigured Che workspace using a dedicated toolset.

Instead of IDE, specialized tools are provided in EclipseCe. Build your own, based on Eclipse Theia, or choose an existing one, such as Jupyter.

Market (soon), easy to distribute tools and custom IDE, can be tried online, to users and the community. EclipseChe uses Che-Theia as the default browser-based IDE. Theia provides a framework for building WebIDE. It is built in TypeScript and provides a flexible programming model for contributors that relies on state-of-the-art tool protocols and makes it faster to build new tools.

In EclipseCe, the dependencies required by tools running in the user's workspace are available when needed. This means that the Che-Theia plug-in provides its dependencies, its back-end services (which can be run in a Sidecar container connected to the user's workspace), and IDEUI extensions. Package all these elements together so that users don't have to configure different tools together.

VisualStudio code extension compatibility

EclipseCHE will rationalize the efforts of contributors who want to build plug-ins and distribute them to different developer communities and tools. For this reason, the function of EclipseCHE is the plug-in API, which is compatible with the extension point of VisualStudio code. Therefore, it is easy to bring existing plug-ins from VisualStudio code to EclipseCHE. The main difference lies in the way plug-ins are encapsulated. On EclipseCHE, plug-ins have their own dependencies in their own containers.

Enterprise integration

EclipseChe includes Keycloak to handle authentication and security. It allows integration with any single sign-on (SSO) as well as ActiveDirectory or LDAP. Each EclipseChe user has access to a centralized developer workspace that can be easily defined, managed, and managed. As a native Kubernetes application, EclipseChe integrates with Prometheus and Grafana to provide state-of-the-art monitoring and tracking capabilities.

At this point, I believe you have a deeper understanding of the "detailed introduction of Eclipse Che 7". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.