1- EMQ X configuration file is in [ HOCON] ( https://github.com/emqx/hocon ) format.
1+ EMQX configuration file is in [ HOCON] ( https://github.com/emqx/hocon ) format.
22HOCON, or Human-Optimized Config Object Notation is a format for human-readable data,
33and a superset of JSON.
44
55## Layered
66
7- EMQ X configuration consists of 3 layers.
7+ EMQX configuration consists of 3 layers.
88From bottom up:
99
10101 . Immutable base: ` emqx.conf ` + ` EMQX_ ` prefixed environment variables.<br >
@@ -36,7 +36,7 @@ node.name="127.0.0.1"
3636node.cookie="mysecret"
3737```
3838
39- This flat format is almost backward compatible with EMQ X 's config file format
39+ This flat format is almost backward compatible with EMQX 's config file format
4040in 4.x series (the so called 'cuttlefish' format).
4141
4242It is 'almost' compatible because the often HOCON requires strings to be quoted,
@@ -51,13 +51,13 @@ For more HOCON syntax, please refer to the [specification](https://github.com/li
5151
5252## Schema
5353
54- To make the HOCON objects type-safe, EMQ X introduced a schema for it.
54+ To make the HOCON objects type-safe, EMQX introduced a schema for it.
5555The schema defines data types, and data fields' names and metadata for config value validation
5656and more. In fact, this config document itself is generated from schema metadata.
5757
5858### Complex Data Types
5959
60- There are 4 complex data types in EMQ X 's HOCON config:
60+ There are 4 complex data types in EMQX 's HOCON config:
6161
62621 . Struct: Named using an unquoted string, followed by a predefined list of fields,
6363 fields can not start with a number, and are only allowed to use
@@ -85,11 +85,11 @@ There are quite some different primitive types, to name a few:
8585* ...
8686
8787The primitive types are mostly self-describing, some are built-in, such
88- as ` atom() ` , some are defined in EMQ X modules, such as ` emqx_schema:duration() ` .
88+ as ` atom() ` , some are defined in EMQX modules, such as ` emqx_schema:duration() ` .
8989
9090### Config Paths
9191
92- If we consider the whole EMQ X config as a tree,
92+ If we consider the whole EMQX config as a tree,
9393to reference a primitive value, we can use a dot-separated names form string for
9494the path from the tree-root (always a Struct) down to the primitive values at tree-leaves.
9595
@@ -181,7 +181,7 @@ zone.zone1.mqtt.max_packet_size = 10M
181181
182182#### Array Elements
183183
184- Arrays in EMQ X config have two different representations
184+ Arrays in EMQX config have two different representations
185185
186186* list, such as: ` [1, 2, 3] `
187187* indexed-map, such as: ` {"1"=1, "2"=2, "3"=3} `
0 commit comments