Sunday, 2019-07-21

*** factor has joined #opendev00:01
*** factor has quit IRC00:03
*** factor has joined #opendev00:03
openstackgerritJames E. Blair proposed zuul/zuul master: WIP download and display a log file
openstackgerritVEDA proposed opendev/irc-meetings master: Updated the PowerVM Chair Person Info
*** icarusfactor has joined #opendev15:49
*** factor has quit IRC15:49
*** cerr has joined #opendev16:12
*** cerr has quit IRC16:12
*** stdcerr has joined #opendev16:15
stdcerrHi all, i've got a question regarding configuration files: is it preferred to have one single big file or multiple smaller config files?16:17
*** icarusfactor has quit IRC16:22
fungistdcerr: configuration files for what?16:43
stdcerrfungi: for a project I'm working on16:44
fungistdcerr: i mean, configuration for what sort of software?16:44
fungiare you asking in general about design principles when deciding how to implement configuration for software, or is there some specific opendev service you're trying to configure (zuul? something else?)16:45
stdcerrfungi: it's a general question about design principles....16:50
stdcerrI understand that this is subjective but is there a preferred "GNU way"?16:50
stdcerrI think it generally gets all lumped together into one single large file...16:51
stdcerrthinking of emacs configurations e.g. (even though I'm a vim user)16:51
fungito a great extent it depends on the complexity of your configuration language, i my opinion16:54
fungifor some complex services i prefer "run-parts" (think rc.d) type modular multi-file configuration with explicit ordering16:55
fungifor others, sure a single conffile makes things easier16:56
fungialso sometimes fewer conffiles means easier templating for configuration management16:56
fungithe downside to large and complicated configs comes at upgrade when you need to fold your local changes into the upstream defaults16:57
fungisoftware which uses sane defaults and a minimum of required configuration parameters can mitigate that, however16:57
fungiso for me at least, there's no cut-and-dried answer. the above are what i tend to take into consideration when deciding16:58
fungialso, i'm more of a sysadmin than a developer, so my preferences tend to err on the side of ease of operation and use rather than ease of development and distribution16:59
*** factor has joined #opendev17:49
stdcerrfungi: Thanks for your feedbacck! It's great to hear opinions! :)18:59
stdcerri thin my complete config will be small enogh to keep it ina simngle file.... think of it like a very elbaborte samba connfig with variouss shares... all shares are in the same file instad o a separate file per share....19:01
*** stdcerr has quit IRC19:03
*** stdcerr has joined #opendev19:08
*** factor has quit IRC19:52
*** factor has joined #opendev19:53
*** factor has quit IRC19:56
openstackgerritMatthew Thode proposed openstack/diskimage-builder master: support alternate portage directories

Generated by 2.15.3 by Marius Gedminas - find it at!