# Che-machine-exec

Che-machine-exec is a Golang server that spawns and manages terminal and command processes within Eclipse Che workspaces. It is open source and self-hosted, installable on Docker Hub.

Canonical page: https://ourlocalhost.com/app/6178/che-machine-exec

## Description

Che Machine Exec is a Golang server that spawns and manages terminal and command processes within Eclipse Che workspaces. It uses the JSON-RPC protocol to communicate with clients and serves as the execution backend for the Eclipse Che cloud development platform, intended for operators deploying Che.

## Platform availability

Available on 0 of 10 platforms.

## Health score

64/100 (Good), based on 5 of 5 factors.
- Maintained: 100 (last commit 19 days ago)
- Popular: 22 (12 GitHub stars)
- Easy to install: 25 (0 install platforms, install notes, Docker image)
- Light to run: 70 (750 MB minimum RAM)
- Security check: 80 (no serious findings, 2 minor, CI, tests, OpenSSF Scorecard 6.7/10)

## Links

- Docker Hub: https://hub.docker.com/r/eclipse/che-machine-exec
- GitHub: https://github.com/eclipse-che/che-machine-exec

## Common questions

### What protocol does che-machine-exec use to communicate with clients?

It uses the JSON-RPC protocol to communicate with the client.

### Which Minikube add-ons should be enabled when installing Che?

Start Minikube with the ingress and dashboard add-ons, and provide the listed memory, CPU, and disk settings. Che needs those built-in parts and enough headroom, or the dashboard and workspaces can fail to start.

### How can a user know a Che workspace is ready to use?

Run the get devworkspaces command after starting a devworkspace and wait until the PHASE column says Running. It first shows Starting while the environment is being built, so it is not usable until that finishes.

### What storage check is needed if FUSE is enabled for Che workspaces?

Run podman info after starting a workspace and confirm the storage driver is overlay. A different driver can cause files or permissions to fail inside the workspace.

### What behavior does an open che-machine-exec issue request?

It asks that che-machine-exec not fail with a help log.fatal message. It also asks that critical messages be logged and sent to the client.

## Alternatives

- ActiveState Komodo IDE: ActiveState Komodo IDE is a retired, open-source, cross-platform integrated development environment for developers to edit, debug, and mana…
- Apache NetBeans: A free, open-source Integrated Development Environment for software developers.
- GNU Emacs: GNU Emacs is an extensible, customizable text editor—and more.
- Geany: Geany is a powerful, stable and lightweight programmer's text editor that provides tons of useful features without bogging down your workfl…
- Gram: Gram is a powerful and modern source code editor.
- Helix
- IntelliJ IDEA: IntelliJ IDEA is a Java-based integrated development environment (IDE) offering intelligent code completion, refactoring, and debugging too…
- Microsoft Visual Studio: Microsoft Visual Studio is an IDE used to create programs, apps, websites, and web services using various frameworks.
- Neovim: Refactored version of Vim with enhanced extensibility and modern plugin architecture.
- PyCharm: IDE for Python and Django offering refactoring, code analysis, VCS integration, debugger, deployment, and more, with a Community Edition op…
- Qodana Python: Qodana for Python is a quality-monitoring tool that scans your code for errors, security flaws, and inefficiencies.
- VSCodium: VSCodium is a community-driven, freely-licensed binary distribution of Microsoft's VS Code.

---
Source: Our Local Host (https://ourlocalhost.com/app/6178/che-machine-exec), the self-hosted and open-source app directory.
