https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31059
--- Comment #9 from David Cook <[email protected]> --- (In reply to Jonathan Druart from comment #7) > And... Why not simply doing it in a db rev? Fail the upgrade until the key > exists in the config: we provide info about how to generate the key and add > it to the config. A people doing the Koha upgrade is supposed to know how to > run a command and edit a file on the server. I think this would cause a lot of headaches, but it's an interesting point. I still like the idea of a machine-generated config file that we can update (for example via a db rev). Or... koha-conf.xml becomes a generated file. We can have a separate file for local updates, and it can be used with program logic to generate the koha-conf.xml That could automatically keep koha-conf.xml up-to-date. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug. _______________________________________________ Koha-bugs mailing list [email protected] https://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/
