To configure Continuum, select Administration from the right-side menu, then Settings on the top menu. Select the System tab on the left edge of the page.
Almost every setting required for Continuum has a built-in default value. Since Continuum can run on one or more hosts, the mechanism for loading configuration is flexible and suitable for this distributed setup.
All Continuum processes follow a simple method for calculating their settings when they start:
Start with hardcoded configuration defaults.
Read the continuum.yaml file on the host. (/etc/continuum/continuum.yaml by default)
Encryption key is the only required value in this file.
MongoDB properties may be provided, as a Mongo connection is required to read the complete configuration.
Read any custom configuration from the database.
Revisit the continuum.yaml file, this time loading any local settings for this specific host.
There are many settings in Continuum - some services or features allow one or two settings, others require quite a bit more. Following are details about the System specific configuration properties.
See the other documents in this section for service/feature specific details.
Every Continuum host must have an /etc/continuum/continuum.yaml file, and at a minimum that file must have a service section with an encryption key. Most commonly, this file contains a handful of settings necessary to tell Continuum services details about the database, temp and logging directories, etc.
Here's a typical minimum continuum.yaml file as generated by the installer:
system: key: GzyRvxtUfzT02C68uzRlEg== mongodb_database: continuum uicache: /var/continuum/ui tmpdir: /var/continuum/tmp logfiles: /var/continuum/log
The encryption key is used to encrypt all sensitive data. DO NOT change this setting manually, it must be set by the install script. If you change this key and forget the original value, all encrypted data in the database will be unrecoverable. Contact email@example.com if you need to change your encryption key on an existing installation.