Add multiuser environment variables

Author: sleshchenko

dockerfiles/init/manifests/che.env

@@ -507,3 +507,57 @@ CHE_KEYCLOAK_PRIVATE_REALM=che
 CHE_KEYCLOAK_PRIVATE_CLIENT__ID=che
 CHE_KEYCLOAK_PRIVATE_CLIENT__SECRET=2c1b2621-d251-4701-82c4-a7dd447faa97
 
+########################################################################################
+#####                                                                              #####
+#####                             WORKSPACE LIMITS                                 #####
+#####                                                                              #####
+#
+# Workspaces are the fundamental runtime for users when doing development. You can set
+# parameters that limit how workspaces are created and the resources that are consumed.
+#
+#     The maximum number of workspaces that a user is allowed to create. The user will
+#     be presented with an error message if they try to create additional workspaces.
+#     This applies to the total number of both running and stopped workspaces. Since
+#     each workspace is saved as a snapshot, placing a cap on this number is a way
+#     to limit the disk consumption for workspace storage.
+#CHE_LIMITS_USER_WORKSPACES_COUNT=-1
+
+#     The maximum number of running workspaces that a single user is allowed to have.
+#     If the user has reached this threshold and they try to start an additional
+#     workspace, they will be prompted with an error message. The user will need to
+#     stop a running workspace to activate another.
+#CHE_LIMITS_USER_WORKSPACES_RUN_COUNT=-1
+
+#     The total amount of RAM that a single user is allowed to allocate to running
+#     workspaces. A user can allocate this RAM to a single workspace or spread it
+#     across multiple workspaces.
+#CHE_LIMITS_USER_WORKSPACES_RAM=-1
+
+#     The total amount of RAM that a single organization (team) is allowed to allocate
+#     to running workspaces. An organization owner can allocate this RAM however they
+#     see fit across the team's workspaces.
+#CHE_LIMITS_ORGANIZATION_WORKSPACES_RAM=-1
+
+#     The maximum number of workspaces that a organization is allowed to own. The
+#     organization will be presented an error message if they try to create
+#     additional workspaces. This applies to the total number of both running
+#     and stopped workspaces. Since each workspace is saved as a snapshot, placing a
+#     cap on this number limits the disk consumption for workspace storage.
+#CHE_LIMITS_ORGANIZATION_WORKSPACES_COUNT=-1
+
+#     The maximum number of running workspaces that a single organization is allowed.
+#     If the organization has reached this threshold and they try to start an
+#     additional workspace, they will be prompted with an error message. The
+#     organization will need to stop a running workspace to activate another.
+#CHE_LIMITS_ORGANIZATION_WORKSPACES_RUN_COUNT=-1
+
+#     The length of time that a user is idle with their workspace when the system will
+#     suspend the workspace by snapshotting it and then stopping it. Idleness is the
+#     length of time that the user has not interacted with the workspace, meaning that
+#     one of our agents has not received interaction. Leaving a browser window open
+#     counts toward idleness.
+#CHE_LIMITS_WORKSPACE_IDLE_TIMEOUT=-1
+
+#     The maximum amount of RAM that a user can allocate to a workspace when they
+#     create a new workspace. The RAM slider is adjusted to this maximum value.
+#CHE_LIMITS_WORKSPACE_ENV_RAM=16gb