This guide focuses on the configuration of the web-client of conjoon. For more information on the configuration of one of the available backends, please refer to the Backend Guide
conjoon is a set of packages that need to get activated with the main application in order to work. This guide shows how to use the central configuration file for the whole application, and how to adjust package-specific settings.
Where can I find the configuration file?
The configuration file for conjoon is available at the following path in a build:
What goes into a
An overview of a conjoon configuration can be categorized into:
For exact reference to each of the configurable fields, you may refer to the conjoon.conf.json reference.
packages-section in the configuration file of conjoon allows for configuring package-specific behavior.
Although packages are self-contained and can be configured directly within their domain, it is good practice to
configure them in the configuration file of conjoon. It also allows you for adding
controller plugins, altering the functionality of packages.
During runtime, Application- and Package-specific configurations can be accessed with the
services-section allows for configuring services to be looked up for the ServiceLocator in conjoon, making it possible to share existing functionality among the unlinked packages used with conjoon.
If you are interested in how the ServiceLocator works with conjoon, you can follow this guide.
Plugins are divided into
component-plugins, and allow for altering the functionality of components and the application itself.
If you are interested in the internals of the configuration system and how it is used with conjoon, you can refer to this guide.