This page describes how to configure a Cloudomation workspace.
Cloudomation workspaces can be configured directly in the workspace or through environment variables contained in a configuration file on the server. Not all configuration options are available in both places, particularly fundamental configurations like database access can only be set via environment variables. All configuration options have a built-in default value.
The order of application of workspace configuration values is:
- Manually set values in the workpsace configuration directly in the workspace. If none is set:
- Manually set values in the environment variables configuration file (on the server). If none is set:
- Default values
Workspace Configuration in the Workspace
There is currently no UI screen available to edit environment variables. This feature ist under development and will be released soon. Currently, environment variables in the workspace can only be edited via the REST API. Reach out to email@example.com if you need help adjusting your workspace configuration.
Refer to the REST API documentation under the header "System" for information on how to access and update the workspace configuration via the REST API. Refer to Workspace Configuration Options for a list and description of all available options.
To be able to change
workspace_configuration via the REST API the calling identity must have
UPDATE permissions on the
workspace record type.
For on-premise installations these options can be set by users managing the Cloudomation installation as environment variables on the docker containers. For cloud installations the options are managed by us. Please get in touch with firstname.lastname@example.org to request a change.
Below table shows all recognized options and their description for configuration options which can only be set in the environment variables. Please note that all options listed in Workspace Configuration Options can also be set via environment variables.
Note the order of application of environment variables: if an option is set both in environment variables, as well as in the workspace directly, the option configured in the workspace directly will take precedence over the option set in the environment variables.
Some of the settings are applicable for the workspace container, others for the auth container, some for both. For on-premise installations the values can be set in
|Path to a writable unix-domain-socket file used for communication between the workspace and the sandbox. The workspace will create the file.|
|If non-empty, the workspace will not create |
|The IP address the REST API will bind to.|
|The port number the REST API will bind to.|
|The hostname of the Cloudomation database.||required|
|The port number of the Cloudomation database.|
|The name of the Cloudomation database.||required|
|The username used to authenticate against the database.||required|
|The password used to authenticate against the database.|
|Path to a file containing the database password.|| required if |
|Path to the databases certificate file.|
|Path to a database client certificate file.|
|Path to a database client certificate key file.|
|Temporary path for the GIT connector.|
|Temporary path where the git repositories are synced to.|
|The hostname of the SMTP server used to send notifications.|
|The port number of the SMTP server.|
|If to use the SMTP "usetls" command.|
|The username used to authenticate against the SMTP server.|
|The password used to authenticate against the SMTP server.|
|Path to a folder where internal notifications are written to. Only used when no SMTP connection is configured.|
|If to periodically write a usage report.|
|The path where usage report is written to.|
|The domain where your workspace is accessible. Used to generate links to the workspace in mails.||required|
|The subdomain where your workspace is accessible. Used to generate links to the workspace in mails.||required|
|The FQDN to your workspace. Used to generate links to the workspace in mails.||required|
|The URL where Cloudomation extensions are fetched from|
|A comma separated list of extensions which are fetched on workspace startup|
All license settings are only applicable for the workspace container.
|The ID of the workspace installation.||required|
|The name of the workspace.||required|
|The ID of the organization.||required|
|The name of the organization.||required|
|An API key used for the communication between the workspace and the license server.||required|
|The number of hours a login token remains valid after login. Cannot be more than |
|The number of hours an invitation code is valid. Cannot be more than |
|The number of hours a recovery code is valid. Cannot be more than |
|Number of failed login attempts before a Cloudomation user is locked out. Cannot be less than |
|Path to the public RSA key used to verify login tokens.||required|
|Path to the private RSA key used to generate login tokens.||required|
|Path to the previous public RSA key used to verify login tokens during key rotation.|
|The value used for the SameSite cookie flag of login tokens. One of |
|The email address of the initial user of the workspace. This use cannot be renamed or deleted and has all permissions.||required|
|After how many minutes of inactivity development-mode executions will be paused.|
|The proxy server to use for http:// requests. Eg. |
|The proxy server to use for https:// requests. Eg. |
|The proxy server to use for ws:// (web-socket) requests. Eg. |
|The proxy server to use for wss:// (web-socket secure) requests. Eg. |
|If set to |
All performance settings are only applicable for the workspace container.
|How often to register the process as "alive" in the database. If the database does not respond within this timeout the process will shut down.|
|A process which did not register as "alive" after this timeout will be considered "dead" and removed from the database.|
|How often to synchronize git repositories (in seconds).|
|The number of seconds between checks of the primary process.|
|The number of seconds between database consistency checks.|
|The number of bytes to read from a file at once.|
|Executions being idle longer than this setting will be unloaded from memory.|