The YAML file is constructed with keys and entities, using the following format:
configVersion: 1 ... # common database used by all mission_control services shared: database: type: postgresql host: localhost port: 5432 name: mission_control ... ... ...
Configuration values are applied according to the following hierarchy:
If the user does not set any values in any of the files above, the application will use the default settings of the application.
The system yaml templates (
Once you have configured your YAML file to include all the configuration changes needed, you can apply them by restarting the server
Modifying the system configurations is an advanced feature. Since it is easy to overwrite configurations, it is strongly recommended backing up the configuration before making any direct changes, and taking great care when doing so.
As explained above, each product in the JFrog Platform has its own
system.yaml file that enables you to configure its behavior. Each YAML file, however, includes both shared configurations - which apply to all of the JFrog Platform products - and dedicated operational microservices configurations, which are relevant only to that product.