Your first-day experience

Che creates a cloud development environment (CDE) for your project. The dashboard and CLI refer to each CDE as a workspace. Each cloud development environment runs as a Kubernetes DevWorkspace custom resource on your cluster. You go from login to coding in about three minutes.

From URL to code in four steps

When your administrator shares the Che dashboard URL, you go from login to coding in four steps:

  1. Authenticate with Kubernetes — Che redirects you to the Kubernetes OAuth login page. Enter your Kubernetes credentials and authorize Che to access your account.

  2. Create Workspace page — After authentication, you land on the Create Workspace page. The page has two main sections:

    • Git Repo URL — A field where you paste the HTTPS or SSH URL of your Git repository.

    • Select a Sample — Pre-configured samples for languages and frameworks such as Java, Node.js, Python, and Go. Use these to explore Che without connecting your own repository.

  3. Start your cloud development environment — When you enter a Git URL and click Create & Open, Che asks you to confirm that you trust the repository authors, then provisions the cloud development environment.

  4. IDE loads in your browser — The default IDE, Microsoft Visual Studio Code - Open Source, opens in your browser tab with the repository already cloned.

Why the first start takes longer

The first cloud development environment start takes approximately 2-3 minutes because Che pulls container images to the cluster node. The starting page displays real-time progress, including:

  • Volume provisioning for persistent storage

  • Container image pulls for the development tools and IDE

  • Initialization of the project clone, home directory, and IDE server

Subsequent starts are faster because Kubernetes caches the container images on the node. If your administrator has deployed the Image Puller, images are pre-cached across all nodes for near-instant starts.

Administrators can reduce first-start times by pre-caching container images on cluster nodes.

What you can do in a cloud development environment

A running cloud development environment provides:

Terminal

A bash terminal in the IDE with your project directory as the working directory. The terminal prompt shows the current Git branch.

Git integration

Your repository is cloned into the cloud development environment filesystem. If your administrator has configured OAuth for your Git provider, you can push commits without re-entering credentials.

Development tools

The Universal Developer Image (UDI) includes compilers, runtimes, and build tools for common languages. Your project’s devfile.yaml can define additional tools and commands.

CDE URL

Each cloud development environment has a unique URL in the format https://<che_fqdn>/<user_name>/<workspace_name>/. Bookmark this URL to return to a running cloud development environment.

Troubleshoot common issues

Cloud development environment fails to start with OOMKilled or FailedScheduling

Your namespace exceeded its resource quota, or the cloud development environment requested more memory or CPU than the cluster allows. Contact your administrator to adjust resource limits.

Git push returns 401 Unauthorized or 403 Forbidden

OAuth is not configured for your Git provider, or your token has expired. Configure authentication to resolve this issue.

Blank IDE with a Could not register service workers error

This error occurs in Google Chrome Incognito mode or Mozilla Firefox Private Browsing mode. Use a regular browser window instead.

Additional resources

Joining the community

Public chat

Join the public Eclipse Cloud Dev Tools Working Group on Slack and the #forum-che channel to chat with the developers.

GitHub project repositories

Report bugs, request features, and contribute in the main Eclipse Che repository.

Community meetings

Join us in the Che community meeting, available on-demand.