A Setting is an essential bit of ConfigCat. It can represent a feature flag/toggle, a number or any text your application requires to be modified without the need of a new deployment.
Anatomy of a Setting
|Name||A human readable name that differentiates the Setting on the ConfigCat Dashboard. e.g., |
|Key||A variable name within your code. e.g., |
|Type||Type of information you'd like to keep in the Setting. e.g., On/Off Toggle, Text, Number|
|Value||The actual value of your Setting. e.g., |
About Setting types:
|Setting Kind||Setting Type||Description|
|On/Off Toggle||Boolean||true/false, usually the state of a feature flag|
|Text||String||any string, max. 65535 characters|
|Whole Number||Integer||any whole number within the range of |
|Decimal Number||Double||any decimal number within the range of |
A Config is a collection of Settings. Configs help you organize settings around topics, or around your software components. A Config is like an online version of a traditional config file.
An environment in ConfigCat represents an environment in your development lifecycle (like production, staging, development etc.). Different environments have the same settings but can have different values.
Each environment-config pair has its own SDK Key which must be used to initialize the ConfigCat SDK within your application.
A collection of Configs, Environments and Team members. A Product typically represents your application (or your service) and the people working on it. It might be a good idea to invite others to your Product to collaborate.