You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whazzup is a service that may be installed on multiple components within a single environment. Due to this fact, the config file will look different depending on which service(s) are running on the host it's installed on.
Most people will use configuration management to install whazzup and generate its config file. In the current case, it's required that we gate portions of the config with conditional logic so that we can expose only the relevant config bits... otherwise, we will have lots of dependencies and be leaking sensitive information (like db passwords) in places where they're not needed.
Instead, whazzup should use conf.d-style configuration. This will allow for a 1:1 mapping between configuration files and services... which will enable users to cleanly separate the CM code for generating various whazzup configs on a per-service basis.
The text was updated successfully, but these errors were encountered:
Whazzup is a service that may be installed on multiple components within a single environment. Due to this fact, the config file will look different depending on which service(s) are running on the host it's installed on.
Most people will use configuration management to install whazzup and generate its config file. In the current case, it's required that we gate portions of the config with conditional logic so that we can expose only the relevant config bits... otherwise, we will have lots of dependencies and be leaking sensitive information (like db passwords) in places where they're not needed.
Instead, whazzup should use conf.d-style configuration. This will allow for a 1:1 mapping between configuration files and services... which will enable users to cleanly separate the CM code for generating various whazzup configs on a per-service basis.
The text was updated successfully, but these errors were encountered: