4.5 Configuration Directories [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

====== 4.5 Configuration Directories ======

[[fxdemo:05-part:start | Go To Top ]]

[[fxdemo:05-part:04-repository-layout:start | Return to Repository Layout ]]

The ''config/'' directory should contain [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]] files that developers and runtime scripts use to build, run, observe, and validate the Phase 0 [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]]. These may include [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] Configuration files, [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] Configuration files, [[dido:99_annexes:annex-b-terms-and-definitions:q:qos|QoS]] profile files, container Configuration files, logging Configuration files, and demonstration Configuration files.

A representative structure is:

<code>
config/
    nodes/
    dds/
    qos/
    logging/
    demo/
</code>

Configuration files should use predictable names and should avoid machine-specific assumptions. They should not depend on absolute local paths, developer-specific usernames, personal directories, or unrecorded environment variables.

Where Configuration values differ across environments, the team should use templates, sample files, or documented environment variables. The [[dido:99_annexes:annex-b-terms-and-definitions:r:repository|Repository]] should distinguish shared Baseline Configuration from local developer overrides.

----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>