Open shikazu opened 8 years ago
INI looks less complicated for startup options only. Also INI could be easier edited by orchestration tools like saltstack and such.
JSON is more suitable for output and parsing stuff, and XML looks a little too legacy and visualy complex for such task, but it's IMHO.
JSON will also be used for communication over pub/sub.
INI cant be used to build a tree, so i would prefer JSON over INI.
Some projects using YAML as configuration format (tree supported), but if it's not exists in current framework/libraries, I suppose JSON would fit
Lets hear some other opinions.
For me it's just changing 2 lines of code :D
I would like to know which Configuration Filetype you prefer or you think suits best for Connection Information to Redis, MongoDB and Ports of the Servers.
I give you the following options:
All other Configuration options will be saved within MongoDB and Distributed over pub/sub after launch.