|
933 | 933 | </li>
|
934 | 934 |
|
935 | 935 | <li class="md-nav__item">
|
936 |
| - <a href="#three-scopes-of-configuration" class="md-nav__link"> |
| 936 | + <a href="#four-scopes-of-configuration" class="md-nav__link"> |
937 | 937 | <span class="md-ellipsis">
|
938 |
| - Three Scopes of Configuration |
| 938 | + Four scopes of configuration |
939 | 939 | </span>
|
940 | 940 | </a>
|
941 | 941 |
|
|
1338 | 1338 |
|
1339 | 1339 |
|
1340 | 1340 |
|
| 1341 | + <li class="md-nav__item"> |
| 1342 | + <a href="../DebugUiConfiguration/" class="md-nav__link"> |
| 1343 | + |
| 1344 | + |
| 1345 | + <span class="md-ellipsis"> |
| 1346 | + Debug UI |
| 1347 | + </span> |
| 1348 | + |
| 1349 | + |
| 1350 | + </a> |
| 1351 | + </li> |
| 1352 | + |
| 1353 | + |
| 1354 | + |
| 1355 | + |
| 1356 | + |
| 1357 | + |
| 1358 | + |
| 1359 | + |
| 1360 | + |
| 1361 | + |
1341 | 1362 | <li class="md-nav__item">
|
1342 | 1363 | <a href="../Migrating-Configuration/" class="md-nav__link">
|
1343 | 1364 |
|
@@ -2295,15 +2316,16 @@ <h2 id="base-directory">Base Directory</h2>
|
2295 | 2316 | default behavior of scanning the base directory for input files. Scanning is overridden
|
2296 | 2317 | independently for each file type, and can point to remote cloud storage with arbitrary URIs.
|
2297 | 2318 | See <a href="./#Storage">the storage section</a> for further details.</p>
|
2298 |
| -<h2 id="three-scopes-of-configuration">Three Scopes of Configuration</h2> |
2299 |
| -<p>OTP is configured via three configuration JSON files which are read from the directory specified on |
| 2319 | +<h2 id="four-scopes-of-configuration">Four scopes of configuration</h2> |
| 2320 | +<p>OTP is configured via four configuration JSON files which are read from the directory specified on |
2300 | 2321 | its command line. We try to provide sensible defaults for every option, so all three of these files
|
2301 | 2322 | are optional, as are all the options within each file. Each configuration file corresponds to
|
2302 | 2323 | options that are relevant at a particular phase of OTP usage.</p>
|
2303 | 2324 | <p>Options and parameters that are taken into account during the graph building process will be "baked
|
2304 | 2325 | into" the graph, and cannot be changed later in a running server. These are specified
|
2305 | 2326 | in <code>build-config.json</code>. Other details of OTP operation can be modified without rebuilding the graph.
|
2306 |
| -These run-time configuration options are found in <code>router-config.json</code>. Finally, <code>otp-config.json</code> |
| 2327 | +These run-time configuration options are found in <code>router-config.json</code>. If you want to configure |
| 2328 | +the built-in debug UI add <code>debug-ui-config.json</code>. Finally, <code>otp-config.json</code> |
2307 | 2329 | contains simple switches that enable or disable system-wide features.</p>
|
2308 | 2330 | <h2 id="configuration-types">Configuration types</h2>
|
2309 | 2331 | <p>The OTP configuration files use the JSON file format. OTP allows comments and unquoted field names
|
|
0 commit comments