On 05/02/2017 12:03 PM, sebb wrote: > On 1 May 2017 at 18:40, Ulises <[email protected]> wrote: >> Not just for not technically minded people (and techies too) but also >> easier (possibly) to handle during automated deployments. > > How so?
I'm not Ulises, but I'd think some of the reasoning is that most config management today is centered around yaml - so going from yaml (in cfg mgmt) to yaml (in PM) would be easier than trying to convert to a custom lua script. > >> You got my +1 here. >> >> U >> >> On Mon, May 1, 2017, 12:35 Daniel Gruno <[email protected]> wrote: >> >>> While having a cup of coffee on the balcony, I got to thinking - would >>> it make sense for us to convert the PM UI configuration to yaml instead >>> of a .lua file? It should make it less arcane to edit for non-techies. >>> >>> The config could be something like this: >>> >>> # ElasticSearch settings >>> database: >>> host: "http://localhost:9200/"; >>> db: "ponymail" >>> secure: false >>> >>> # Outgoing email settings >>> smtp: >>> host: "localhost:25" >>> accepted_domains: >>> - "apache.org" >>> - "*.apache.org" >>> >>> # User Interface settings >>> ui: >>> wordcloud: false >>> slow_count: true >>> >>> etc etc :) >>> >>> thoughts? > > Is that really easier for the non-techie? > Besides, I don't think a non-techie should change anything in that file. > > Also it would require adding a YAML processor purely to read a single > config file. > > -1 > > If the file really is tricky to edit as it stands, then better > documentation is the answer. > >>> With regards, >>> Daniel. >>>
