[RETHINK] config folder structure and mechanism

HSE applications require paths to be configured for holding configuration information ("_Config" dir) and for storing data ("_Data" dir). Almost all assumptions and definitions for the _Config directory also apply to the _Data directory, because usually, these folders live next to each other in the same base location. Technically, though, both folders can live in completely different locations.

Locations

• In Repo: All folders parallel (next to each other):

  • <%Root%>/<%APP-NAME%>_Source
  • <%Root%>/<%APP-NAME%>_Config
  • <%Root%>/<%APP-NAME%>_Data

• Default for installed application

  • EXE:
    • <%ProgramFiles%>/<%COMP-NAME%>/<%APP-NAME%>/<%APP-NAME%>.exe (readonly)
  • shipping config:
    • <%ProgramData%>/<%COMP-NAME%>/<%APP-NAME%>_Config/ (read-write)
    • <%ProgramData%>/<%COMP-NAME%>/<%APP-NAME%>_Config/Unit_Default/ (readonly)
    • <%ProgramData%>/<%COMP-NAME%>/<%APP-NAME%>_Config/config.ini_default (readonly)

• Default for folders holding the system- or user-specific configuration and data

  • "_Config:
    • <%ProgramData%>/<%COMP-NAME%>/<%APP-NAME%>_Config" (read-write)
  • "_Data":
    • <%ProgramData%>/<%COMP-NAME%>/<%APP-NAME%>_Data" (read-write)

See also #159

Notes

• Modules handle their own config
  • (at least) one config file per module