Changes to "config" between 2018-07-03 21:02:28 and 2018-07-03 21:04:09

12
13
14
15
16
17
18





19

20
21
22
23
24
25
26
12
13
14
15
16
17
18
19
20
21
22
23

24
25
26
27
28
29
30
31







+
+
+
+
+
-
+







plugin handling goes hand in hand with configuration management.
However it requires a structured field to avoid bulky definitions, yet
support enough variation.

Usually `config:` contains multiple indented lines, each being a
<acronym title="JSON, but quotes optional">JSOL</acronym>-dictionary.

<style>
 .cnt-tbl { background: #f7f7f7; }
 .ctn-tbl th { text-align: left }
 .cnt-tbl td { padding: 3pt; border: 2px solid #eee; }
</style>
<table>
<table class="cnt-tbl">
<tr>
   <th><code>name:</code></th>
   <td>associates some variable/constant/expression to a setting.</td>
</tr>
<tr>
<th><code>type:</code></th>
<td> A few common types may cover 90% of configuration needs.