https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31059
--- Comment #12 from Jonathan Druart <[email protected]> --- What I suggested with the db rev was to have a quick solution for this problem. We can of course rethink the whole thing but it's 1 or 2 hours of work vs... X days :) (In reply to Katrin Fischer from comment #8) > (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. > > Hm, I hope noone does a major update unattended, but they might get stuck on > this. Also, you'd need to restart things (Plack, Apache?) would the update > continue fine from there? Yes, this would be part of the "info" we will display: Generate the key using this command, copy the output to the koha-conf into the correct tag, restart everything, try the update again. -- 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] 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/
