<p>The following pages and posts are tagged with <button type="button" style="cursor: default" class="btn btn-default navbar-btn">workspace</button></p> <table><thead><tr><th>Title</th><th>Excerpt</th></tr></thead> <tbody>

<tr><td><a href="commands-ide-macro.html">Commands and IDE Macros</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td>  Commands are script-like instructions that are injected into the workspace machine for execution. Commands are saved in the configuration storage of your workspace and are part of any workspace export.   Command Overview   A command is defined by:  ... </td>
</tr>
<tr><td><a href="creating-starting-workspaces.html">Workspace Management</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td>  Creating Workspaces   The easiest way to create a workspace is to use ready to go stacks in User Dashboard. Images and configuration in these stacks is certified both for Docker and OpenShift, and these are the stacks that are used in daily... </td>
</tr>
<tr><td><a href="debug.html">Debug</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td>  Che currently supports debuggers for:     Java   C/C++ (via GDB)   PHP (via Zend debugger, zDebug and Z-Ray)   Node.js (via GDB)     Java   Java debugger is... </td>
</tr>
<tr><td><a href="dependency-management.html">Dependency Management</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td>  Maven   Currently Eclipse Che provides Maven plugin that is deployed with a workspace agent and started in a separate JVM. The plugin watches for changes in pom.xml, downloads dependencies that updates project’s classpath.   You can forcefully update dependencies for a... </td>
</tr>
<tr><td><a href="editor-code-assistance.html">Editor and Code Assistance</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td>  Orion Editor   Eclipse Che wraps Orion editor to integrate it with language servers, Git, debugger and other servvices that run on server and client side. Use of custom (user provided editors is possible). See: Editor.     Syntax... </td>
</tr>
<tr><td><a href="env-variables.html">Environment variables</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td>  Environment variables are defined per machine. Depending on the infrastructure, they are added either to container or Kubernetes pod definition. You can add, edit and remove environment variables either in User Dashboard or directly in workspace machine configuration:    <span... </td>
</tr>
<tr><td><a href="environments.html">Workspace Environments</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td>  </td>
</tr>
<tr><td><a href="ide-projects.html">Projects and Project Import</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td>  Default Location of Projects   When a workspace machine with a workspace agent starts, the IDE makes calls to Project API to get workspace projects. By default, they are located in projects in a machine container/pod. This location isn’t configurable as many other IDE... </td>
</tr>
<tr><td><a href="installers.html">Installers</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td>  What Are Installers?   Installers are scripts that are injected into machines in a runtime and get executed there to:     Prepare environment and download dependencies for particular software or tool   Install chosen software and dependencies... </td>
</tr>
<tr><td><a href="projects.html">Projects</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td>  Projects in Workspaces   Projects are always associated with a workspace and saved in a workspace configuration:    &quot;projects&quot;: [ { &quot;description&quot;: &quot;A basic example using... </td>
</tr>
<tr><td><a href="recipes.html">Recipes</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td>  Supported Recipe Formats   Depending on the infrastructure, Che supports the following recipes out of the box (default Che build):          ... </td>
</tr>
<tr><td><a href="secure-servers.html">Secure Servers</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td>  Now that you have made yourself familiar with secure servers concept, let’s take a closer look at enabling this functionality and implementation details.   How to enable secure servers functionality?   This functionality is in beta phase now and it is... </td>
</tr>
<tr><td><a href="servers.html">Servers</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td>  What Are Servers   A server defines protocol port of a process that runs in a machine. It also has a name, path, attributes. Path defines base path of service that is exposed via server. Attributes are optional and may be used to tune... </td>
</tr>
<tr><td><a href="stacks.html">Stacks</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td>  What Are Stacks   A stack is a template of workspace configuration and some meta-information like scope, tags, components, description, name and ID. Stacks are used by User Dashboard to make it easy to create workspaces and well as filter sample projects compatible... </td>
</tr>
<tr><td><a href="volumes.html">Volumes</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td>  Default Volumes   By default workspace containers/pods start with one default volume/PVC that persists /projects where workspace projects are physically located. When a workspace is stopped its machines are destroyed, however, volumes stay there.     User-Provided Volumes ... </td>
</tr>
<tr><td><a href="what-are-workspaces.html">What Is a Che Workspace?</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td>  Workspace   Eclipse Che reinvents the definition of a workspace which is usually termed as a local directory with projects and some meta-information that IDE uses to properly configure them. In Eclipse Che, a workspace is the developer environment itself represented by Docker containers,... </td>
</tr>
<tr><td><a href="workspace-data-model.html">Workspace Data Model</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td>   environments: Map&lt;String, getEnvironments&gt; // Workspace envs. A workspace can have multiple envs defaultEnv: STRING // A workspace should have a default environment projects: [] // Projects associated with a workspace commands: [] // Commands associated with a workspace name: STRING // Workspace name that has to... </td>
</tr>
<tr><td><a href="workspaces-rest-api.html">Workspace REST API</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td>  </td>
</tr>
<tr><td><a href="workspaces-troubleshooting.html">Troubleshooting Workspace Start Failures</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td> :page-layout: _auto Failures to start a workspace may be caused by different factors: 1. Environment recipe 2. Network conditions [id="bad-recipes"] == Bad Recipes When a workspace is being started, environment link:recipes.html[recipe] is sent to Docker or OpenShift API. Che server then listens to events provided by a particular infrastructure. In... </td>
</tr>
   </tbody>
</table>