[Koha-bugs] [Bug 13068] New feature for DB update and sandbox

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13068

M. de Rooy <m.de.rooy at rijksmuseum.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |http://bugs.koha-community.
                   |                            |org/bugzilla3/show_bug.cgi?
                   |                            |id=11390

--- Comment #38 from M. de Rooy <m.de.rooy at rijksmuseum.nl> ---
(In reply to David Cook from comment #37)
> I'm juggling a few different projects at the moment, but I'd love to see us
> using deploy() and upgrade().

Added a see also to 11390. We should indeed start using DBIC here.

> Side note: I'm not sure what I think about the syspref "DevUpdateControl".
> It doesn't really seem like a "system preference", so much as a
> configuration item... especially for developers. Why not put this in
> koha-conf.xml and access it via C4::Context? Much less chance of something
> bad happening if an overzealous superlibrarian changes it, I imagine...

It would of course be easy to move it into the conf.xml. But for me it seems to
be just somewhat more a preference than an configuration item. It has a
slightly more dynamic than static nature. But yes, this is an arbitrary choice.

The overzealous superlibrarian-argument doing something bad, is imo not really
relevant. [Side note on the side note: changing marc flavour or various other
prefs would be much more harmful.] Changing this pref on a production machine
should not make a difference, since there should not be dev updates. If there
would be, the superlibrarian should also start install.pl with updatestructure
and he should know the koha admin password. If these three conditions hold, we
are talking about bad maintenance, security and personnel. Running the dev
update(s) at the fourth step would probably not do that much: if they are
there, they are likely to have been executed before. So just some warnings (in
most cases)..

-- 
You are receiving this mail because:
You are watching all bug changes.