http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12824
--- Comment #4 from Robin Sheat <[email protected]> --- I like the idea of a CLI editor/querier for the config. As much as I'm not as anti-XML as many people, I don't think it's the sort of thing that should be hand edited if possible. I'll quibble over details a bit (e.g., they should behave like UNIX commands and be idempotent where possible, whereas your examples aren't, also shouldn't be interactive unless you explicitly ask) but overall it's worthwhile. One this this would lend itself to nicely is automatic configuration, via puppet or such. We might also want an XML schema to describe the config, and we can validate the user input against that perhaps. (Similar to the YAML idea, but it can be used to validate the resulting file in total.) It could be worth looking to the tools that modify the gconf registry for examples on how things should work, as they perform a similar task. gconftool and friends, although they're probably more complicated than we need. As for a GUI, that's not likely to happen. A text UI is fine (debconf-esque or something), but we're not going to ever be depending on a GUI subsystem for a server, servers shouldn't have a GUI. Also, rather than referring people to koha-enable-plugins etc., it should probably subsume them to keep things consistent. Other things to hash out are what happens to elements that can be repeated, nested, and so on. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
