Eclipse Che works with any container, even multi-container runtimes. Run your workspace on Kubernetes and OpenShift. Use an image from DockerHub, Quay.io, your own private registry or one of the many that ship with Che. Add terminal and language services to dev-enable your production images.
Under the hood:
Inject developer services into a workspace with sidecars for syntax auto-complete, error checking and a debugger. Add intellisense for additional languages with language servers. Enable terminal access with the flick of a switch.
Under the hood:
Start working from any device without installing software by using the built-in Eclipse Che IDE. Or stick with the desktop IDE you love by mounting into the Che workspace. Your choice.
Under the hood:
Create custom stacks - runtimes based on your production images, but with the tools your devs need. Anyone can quickly create a production-compliant app by building on a team stack, or duplicating a workspace. Sample code can even be added for training or to start people on the right foot.
Under the hood:
The Language Server Protocol was developed by Microsoft, Red Hat and IBM as a common protocol to provide language services including syntax analysis, outlining, and refactoring within the Eclipse Che, or the IDE or editor of their own choice. The protocol can be used between client tools and language servers to integrate features such as auto complete, goto definition, and find all references. Language server is a term being applied to the language intelligence programs that are providing the services.
Che can inject debugging agents into a developer workspace to allow variable watching and substitutions, breakpoints, step into / over and other common debug operations. Debuggers can be associated with stacks or individual workspaces.
Che enables terminal access to all containers of the workspace. Connect your existing IDE - Eclipse if you like - remotely by syncing /projects folder of your workspace.
A stack is a runtime configuration for a workspace represented by a devfile. It contains components (runtime), projects and commands.
All Che services are reachable through RESTful APIs. Che exposes APIs for managing the workspace server. The Che server provides workspace orchestration and user management.
A no-installation browser IDE and IOE accessible from any local or remote device. Thin, fast, and beautiful - it's the IDE our own engineers wanted. The IDE is packaged as cross-browser JavaScript and CSS, hosted as resources cached by browsers. Work on multiple workspaces in different browser tabs with each tab consuming ~100MB of RAM. It's a smoother interactive experience that doesn't suffer blockages from thrashing when the workspace is remote.
The tools you expect are there: Eclipse Theia editor, numerous key bindings, globalized keyboard support, and git tooling.
Che is a true IDE platform. Projects can be independently built and run, even though all projects share a common workspace container. Che has support for numerous languages by using VS Code extensions and the language server protocol.
A command is a process that is executed into a container. Commands are provided by workspaces or plugins. When executed, a command is translated into a task and executed into a container, where it can operate against projects or other resources within the container itself. Commands are context sensitive, allowing a user to execute commands across projects and modules, getting context-specific outcomes.
Create custom previews that launch files and web pages with the context of your projects and workspaces. Embed preview intelligence inside of commands and workspaces so that logic on how to launch and debug your project travels wherever your workspace goes.
Che, like Yoda, wants to bring balance to the force. Flip a switch and transform the IDE with a dark or light theme.
Che is extensible, by customizing built-in plugins or authoring your own extensions. Package plugins with Che core to create new assemblies installable by your user base. You can write IDE, Che server, or workspace agent plugins, with Che injecting the plug-in into the right location at the right time.
Eclipse Che has been developed over years with contributions from Codenvy, eXo Platform, Red Hat, Salesforce, IBM, SAP, Microsoft, Intuit, WSO2, Serli, and open source individuals from China, Brazil, France, Ukraine, Russia, Canada, India, Sri Lanka, and the United States. It is part of the Eclipse Cloud Development top-level project, and ecosystem contributions are open and encouraged.
Please participate, even if only spiritually. There are many ways to get involved including starring the GitHub repo, submitting issues, writing docs, or contributing plug-ins.
We built the product that we would love to use everyday. To do that you must build what you eat and eat what you built. Love -- and sometimes frustration -- has poured into Che as our engineers weaned off their favorite IDEs to build Che with Che.
