| *** factor has joined #opendev | 00:01 | |
| *** factor has quit IRC | 00:03 | |
| *** factor has joined #opendev | 00:03 | |
| openstackgerrit | James E. Blair proposed zuul/zuul master: WIP download and display a log file https://review.opendev.org/671912 | 00:59 |
|---|---|---|
| openstackgerrit | VEDA proposed opendev/irc-meetings master: Updated the PowerVM Chair Person Info https://review.opendev.org/671929 | 12:12 |
| *** icarusfactor has joined #opendev | 15:49 | |
| *** factor has quit IRC | 15:49 | |
| *** cerr has joined #opendev | 16:12 | |
| *** cerr has quit IRC | 16:12 | |
| *** stdcerr has joined #opendev | 16:15 | |
| stdcerr | Hi 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 IRC | 16:22 | |
| fungi | stdcerr: configuration files for what? | 16:43 |
| stdcerr | fungi: for a project I'm working on | 16:44 |
| fungi | stdcerr: i mean, configuration for what sort of software? | 16:44 |
| fungi | are 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 |
| stdcerr | fungi: it's a general question about design principles.... | 16:50 |
| stdcerr | I understand that this is subjective but is there a preferred "GNU way"? | 16:50 |
| stdcerr | I think it generally gets all lumped together into one single large file... | 16:51 |
| stdcerr | thinking of emacs configurations e.g. (even though I'm a vim user) | 16:51 |
| fungi | to a great extent it depends on the complexity of your configuration language, i my opinion | 16:54 |
| fungi | for some complex services i prefer "run-parts" (think rc.d) type modular multi-file configuration with explicit ordering | 16:55 |
| fungi | for others, sure a single conffile makes things easier | 16:56 |
| fungi | also sometimes fewer conffiles means easier templating for configuration management | 16:56 |
| fungi | the downside to large and complicated configs comes at upgrade when you need to fold your local changes into the upstream defaults | 16:57 |
| fungi | software which uses sane defaults and a minimum of required configuration parameters can mitigate that, however | 16:57 |
| fungi | so for me at least, there's no cut-and-dried answer. the above are what i tend to take into consideration when deciding | 16:58 |
| fungi | also, 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 distribution | 16:59 |
| *** factor has joined #opendev | 17:49 | |
| stdcerr | fungi: Thanks for your feedbacck! It's great to hear opinions! :) | 18:59 |
| stdcerr | i 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 | great! | 19:02 |
| stdcerr | ciao | 19:02 |
| *** stdcerr has quit IRC | 19:03 | |
| *** stdcerr has joined #opendev | 19:08 | |
| *** factor has quit IRC | 19:52 | |
| *** factor has joined #opendev | 19:53 | |
| *** factor has quit IRC | 19:56 | |
| openstackgerrit | Matthew Thode proposed openstack/diskimage-builder master: support alternate portage directories https://review.opendev.org/671530 | 23:22 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!