{"action":"opened","issue":{"url":"https://api.github.com/repos/eclipse/che/issues/2015","repository_url":"https://api.github.com/repos/eclipse/che","labels_url":"https://api.github.com/repos/eclipse/che/issues/2015/labels{/name}","comments_url":"https://api.github.com/repos/eclipse/che/issues/2015/comments","events_url":"https://api.github.com/repos/eclipse/che/issues/2015/events","html_url":"https://github.com/eclipse/che/issues/2015","id":168659266,"number":2015,"title":"Simplify names of all che.properties to be more user friendly","user":{"login":"garagatyi","id":1851863,"avatar_url":"https://avatars.githubusercontent.com/u/1851863?v=3","gravatar_id":"","url":"https://api.github.com/users/garagatyi","html_url":"https://github.com/garagatyi","followers_url":"https://api.github.com/users/garagatyi/followers","following_url":"https://api.github.com/users/garagatyi/following{/other_user}","gists_url":"https://api.github.com/users/garagatyi/gists{/gist_id}","starred_url":"https://api.github.com/users/garagatyi/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/garagatyi/subscriptions","organizations_url":"https://api.github.com/users/garagatyi/orgs","repos_url":"https://api.github.com/users/garagatyi/repos","events_url":"https://api.github.com/users/garagatyi/events{/privacy}","received_events_url":"https://api.github.com/users/garagatyi/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-08-01T14:27:54Z","updated_at":"2016-08-01T14:27:54Z","closed_at":null,"body":"Tyler Jewell:\r\n\r\n> I have gone through and done a revision of the default che.properties file. Every property in a comment `#` is the name of the existing property.  The uncommented names are the proposed new property names. I grouped properties by the end user names that we give to concepts as opposed to the internal names, which are not easily understood.\r\n\r\n```\r\n#\r\n# Copyright (c) 2012-2016 Codenvy, S.A.\r\n# All rights reserved. This program and the accompanying materials\r\n# are made available under the terms of the Eclipse Public License v1.0\r\n# which accompanies this distribution, and is available at\r\n# http://www.eclipse.org/legal/epl-v10.html\r\n#\r\n# Contributors:\r\n#   Codenvy, S.A. - initial API and implementation\r\n#\r\n\r\n### CHE SERVER\r\n# Folder where Che will store internal data objects\r\nche.storage=${che.home}/storage\r\n#che.conf.storage=${che.home}/storage\r\n\r\n# API service. Browsers initiate REST communications to Che server with this URL\r\nche.api=http://localhost:${SERVER_PORT}/wsmaster/api\r\n#api.endpoint=http://localhost:${SERVER_PORT}/wsmaster/api\r\n\r\n### WORKSPACES\r\n# The location where your workspaces (and their projects) are stored by Che server.\r\n# This property works for Docker for Windows, Mac, and Linux.\r\n# On vbox for windows, this property is ignored and workspaces stored:\r\n# c:\\%userprofile%\\AppData\\Local\\Eclipse Che\\\r\nche.workspace.storage=${che.home}/workspaces\r\nche.workspace.storage.create_folders=true\r\n\r\n# Your projects are synchronized from the Che server into the machine running each\r\n# workspace. This is the directory in the ws runtime where your projects are mounted.\r\nche.workspace.projects.storage=/projects\r\n# che.machine.projects.internal.storage=/projects\r\n\r\n# Configures proxies used by runtimes powering workspaces\r\nche.workspace.http_proxy=\r\nche.workspace.https_proxy=\r\nche.workspace.no_proxy=\r\n#http.proxy=\r\n#https.proxy=\r\n#no_proxy=\r\n\r\n# During the stop of the workspace automatically creates a snapshot if the value is {true},\r\n# Otherwise just stops the workspace.\r\nche.workspace.auto_snapshot=true\r\n# workspace.runtime.auto_snapshot=true\r\n\r\n# During the start of the workspace automatically restore it from a snapshot if the value is {true},\r\n# Otherwise create a new workspace.\r\nche.workspace.auto_restore=true\r\n# workspace.runtime.auto_restore=true\r\n\r\n# Java command line options used to start Che agent in workspace runtime\r\nche.workspace.java_opts=-Xms256m -Xmx2048m -Djava.security.egd=file:/dev/./urandom\r\n# che.machine.java_opts=-Xms256m -Xmx2048m -Djava.security.egd=file:/dev/./urandom\r\n\r\n# Folder that will be a volume mount from your host into your workspace.\r\nche.workspace.volume=\r\n# machine.server.extra.volume\r\n\r\n# If your workspace creates SSH connections, their timeouts are managed by this property.\r\nche.workspace.ssh_connection_timeout_ms=3000\r\n# machine.ssh.connection_timeout_ms=3000\r\n\r\n# The location of the Web terminal used within the browser.\r\n# This is copied into the workspace and runs within the workspace.\r\n# Suffix helps differentiate archive for different architectures/OSes\r\nche.workspace.terminal_linux_amd64=${che.home}/lib/linux_amd64/terminal\r\nche.workspace.terminal_linux_arm7=${che.home}/lib/linux_arm7/terminal\r\n#machine.server.terminal.path_to_archive.linux_amd64=${che.home}/lib/linux_amd64/terminal\r\n#machine.server.terminal.path_to_archive.linux_arm7=${che.home}/lib/linux_arm7/terminal\r\n\r\n# Folder where the workspace will store logs from agents and other runtimes\r\nche.workspace.logs=${che.logs.dir}/machine/logs\r\n#machine.logs.location=${che.logs.dir}/machine/logs\r\n\r\n# RAM default for new machines.\r\n# TODO: is this per machine, or for the entire environment?\r\nche.workspace.default_memory_mb=1024\r\n#machine.default_mem_size_mb=1024\r\n\r\n# This archive contains the server to run the workspace agent and any custom extensions.\r\n# Che injects this archive into machines when they are booted or started.\r\n# Each machine can have many agents installed, each located in a different location.\r\nche.workspace.agent[\"dev\"]=${che.home}/lib/ws-agent.zip\r\n#machine.server.ext.archive=${che.home}/lib/ws-agent.zip\r\n\r\n\r\n\r\n# When the Che server launches a new workspace, Che pings a mini Che server running inside of the\r\n# workspace runtime. We call this mini-Che an \"agent\". The Che server knows that the workspace\r\n# is ready for user when the agent returns a valid response.\r\nche.workspace.agent[\"dev\"].max_start_time_ms=60000\r\nche.workspace.agent[\"dev\"].ping_delay_ms=2000\r\nche.workspace.agent[\"dev\"].ping_conn_timeout_ms=2000\r\nche.workspace.agent[\"dev\"].ping_timeout_error_msg=Timeout. The Che server is unable to ping your workspace. This implies a network configuration issue, workspace boot failure, or an unusually slow workspace boot.\r\n#machine.ws_agent.max_start_time_ms=60000\r\n#machine.ws_agent.ping_delay_ms=2000\r\n#machine.ws_agent.ping_conn_timeout_ms=2000\r\n#machine.ws_agent.ping_timed_out_error_msg=Timeout reached. The Che server has been unable to verify that your workspace's agent has successfully booted. Either the workspace is unreachable, the agent had an error during startup, or your workspace is starting slowly. You can configure machine.ws_agent.max_start_time_ms in Che properties to increase the timeout.\r\n\r\n# Hosts listed here will be added to /etc/hosts of each workspace.\r\nche.workspace.hosts=NULL\r\n#machine.docker.machine_extra_hosts=NULL\r\n\r\n# This is the API endpoint of the workspace master running within the core Che server.\r\n# This tells the workspace agent how to connect back to the Che server.\r\n# che-host is a hostname entry added to /etc/hosts of the workspace by the Che server.\r\nche.workspace.che_server_endpoint=http://che-host:${SERVER_PORT}/wsmaster/api\r\n#machine.docker.che_api.endpoint=http://che-host:${SERVER_PORT}/wsmaster/api\r\n\r\n\r\n### TEMPLATES\r\n# Folder that contains JSON files with code templates and samples\r\nche.template.storage=${che.home}/templates\r\n# project.template_description.location_dir=${che.home}/templates\r\n\r\n\r\n### STACKS\r\n# File name containing default stacks definitions\r\nche.stacks.storage=${che.home}/stacks/stacks.json\r\n# che.stacks.default=${che.home}/stacks/stacks.json\r\n\r\n# Folder name where stack images are stored\r\nche.stacks.images=${che.home}/stacks/images\r\n# che.stacks.images.storage=${che.home}/stacks/images\r\n\r\n### AUTHENTICATION PARAMETERS\r\n# Che has a single identity implementation, so this does not change the user experience.\r\n# If true, enables user creation at API level\r\nche.auth.user_self_creation=false\r\n# user.self.creation.allowed=false\r\n\r\nche.auth.access_denied_error_page=/error-oauth\r\n#auth.oauth.access_denied_error_page=/error-oauth\r\n\r\n# Reserved user names\r\nche.auth.reserved_user_names=\r\n# user.reserved_names=\r\n\r\n# You can setup GitHub oAuth to automate authentication to remote repositories.\r\n# You need to first register this application with GitHub oAuth.\r\nche.oauth.github.clientid=NULL\r\nche.oauth.github.clientsecret=NULL\r\nche.oauth.github.authuri= https://github.com/login/oauth/authorize\r\nche.oauth.github.tokenuri= https://github.com/login/oauth/access_token\r\nche.oauth.github.redirecturis= http://localhost:${SERVER_PORT}/wsmaster/api/oauth/callback\r\n#oauth.github.clientid=NULL\r\n#oauth.github.clientsecret=NULL\r\n#oauth.github.authuri= https://github.com/login/oauth/authorize\r\n#oauth.github.tokenuri= https://github.com/login/oauth/access_token\r\n#oauth.github.redirecturis= http://localhost:${SERVER_PORT}/wsmaster/api/oauth/callback\r\n\r\n\r\n### DOCKER PARAMETERS\r\n# Docker is the default machine implementation within Che. Workspaces are powered by machines\r\n# that are constructed when the workspace is started. The images used to generate containers\r\n# for the machines can come from DockerHub or a private Docker registry.\r\nche.docker.registry=${CHE_REGISTRY_HOST}:5000\r\n#machine.docker.registry=${CHE_REGISTRY_HOST}:5000\r\n\r\n# If this is true, then we always pull an image from a registry even if we have an image cached\r\n# locally. If false, Docker only pulls image if it does not exist locally.\r\nche.docker.always_pull_image=true\r\n#machine.docker.pull_image=true\r\n\r\n# If true, then launches all workspace runtime containers with Docker's\r\n# privilged mode. Please use responsibly. This is required if you want Che workspaces\r\n# to be able to launch their own runtimes which are embedded Docker containers.\r\nche.docker.privilege=false\r\n#machine.docker.privilege_mode=false\r\n\r\n# If the browser clients that are accessing Che are remote AND the configuration of Docker is an\r\n# internal IP address or using Unix sockets, then remote browser clients will not be able to connect\r\n# to the workspace. Set the Docker configuration so that Docker containers have an external IP \r\n# address and provide that external host or IP address here. \r\n# This is uncommon, and only needed for advanced Docker configurations.\r\nche.docker.ip=NULL\r\n#machine.docker.local_node_host=NULL\r\n\r\n# Use a Docker registry for workspace snapshots. If false, snaps are saved to disk.\r\nche.docker.registry_for_snapshots=false\r\n#machine.docker.snapshot_use_registry=false\r\n\r\n# Registry snapshot namespace\r\nche.docker.namespace=NULL\r\n#machine.docker.snapshot.registry_namespace=NULL\r\n\r\n# Docker unused containers cleanup period\r\nche.docker.unused_containers_cleanup_min=60\r\n#machine.docker.unused_containers_cleanup_period_min=60\r\n\r\n# Version number of the Docker API used within the Che implementation\r\nche.docker.api=1.20\r\n#docker.api.version=1.20\r\n\r\nche.docker.tcp_connection_timeout_ms=600000\r\n#docker.connection.tcp.connection_timeout_ms=600000\r\nche.docker.tcp_connection_read_timeout_ms=600000\r\n#docker.connection.tcp.read_timeout_ms=600000\r\n\r\n# Docker registry example. Uncomment to add a registry configuration.\r\n# You can configure multiple registries with different names.\r\n#docker.registry.auth.<insert-name>.url=https://index.docker.io/v1/\r\n#docker.registry.auth.<insert-name>.username=<username>\r\n#docker.registry.auth.<insert-name>.password=<password>\r\n\r\n# Allows to adjust machine swap memory by multiplying current machnine memory to provided value.\r\n# default is -1 which is unlimited swap. If set, value is multipled by machine memory set by user \r\n# to determine swap size. To disable swap set to 0.\r\nche.docker.swap=-1\r\n#machine.docker.memory_swap_multiplier=-1\r\n\r\n\r\n### INTERNAL\r\n# Remove locations where internal message bus events should be propagated to.\r\n# For debugging - set to retrieve internal events from external clients.\r\nnotification.server.propagate_events=\r\n\r\n# Che extensions can be scheduled executions on a time basis. \r\n# This configures the size of the thread pool allocated to extensions that are launched on\r\n# a recurring schedule.\r\nschedule.core_pool_size=10\r\n\r\n# Everrest is a Java Web Services toolkit that manages JAX-RS & web socket communications\r\n# Users should rarely need to configure this.\r\n# Disable asynchronous mechanism that is embedded in everrest.\r\norg.everrest.asynchronous=false\r\n# Quantity of asynchronous requests which may be processed at the same time\r\norg.everrest.asynchronous.pool.size=20\r\n# Size of queue. If asynchronous request can't be processed after consuming it will be added in queue.\r\norg.everrest.asynchronous.queue.size=500\r\n# Timeout in minutes for request. If after timeout request is not done or client did not come yet to get result of request it may be discarded.\r\norg.everrest.asynchronous.job.timeout=10\r\n# Size of cache for waiting, running and ended request.\r\norg.everrest.asynchronous.cache.size=1024\r\n# Path to asynchronous service\r\norg.everrest.asynchronous.service.path=/async/\r\n```"}}
{"actor":{"display_login":"garagatyi"}}