Skip to content

Rename env property for setting idle timeout #85

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Rename env property for setting idle timeout #85

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/main/_docs/admin-guide/admin-configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ The total amount of RAM that a single user is allowed to allocate to running wor
The maximum amount of RAM that a user can allocate to a workspace when they create a new workspace. This limit is set by the `CODENVY_LIMITS_WORKSPACE_ENV_RAM` property in the `codenvy.env` file with a default value of `16`gb. The RAM slider is adjusted to this maximum value.

### Idle Timeout
Workspaces have idle timeouts that stop workspaces that a user has not interacted with in a specified time. The idle timeout is set by the `CODENVY_MACHINE_WS_AGENT_INACTIVE_STOP_TIMEOUT_MS` property in the `codenvy.env` file with a default value of `14400000` milliseconds or 4 hours. This allows Codenvy to to free up unused resources but may need to be increased if longer running workspaces are required.
Workspaces have idle timeouts that stop workspaces that a user has not interacted with in a specified time. The idle timeout is set by the `CODENVY_LIMITS_WORKSPACE_IDLE_TIMEOUT` property in the `codenvy.env` file with a default value of `14400000` milliseconds or 4 hours. This allows Codenvy to to free up unused resources but may need to be increased if longer running workspaces are required.

# Docker
Workspace runtimes are powered by one or more Docker containers. When a user creates a workpace, they do so from a [stack]({{base}}{{site.links["ws-stacks"]}}) which includes a Dockerfile or reference to a Docker image which will be used to create the containers for the workspace runtimes. Stacks can pull that image from a public registry, like DockerHub, or a private registry. Images in a registry can be publicly visible or private, which require user credentials to access. You can also set up a private registry to act as a mirror to Docker Hub. And, if you are running Codenvy behind a proxy, you can configure the Docker daemon registry to operate behind a proxy.
Expand Down