search

chrisosaurus / koha-gitify

A script to convert a koha installation (created via koha-create) to run using code in a git clone
GNU General Public License v3.0
8 stars 5 forks source link

Deal with zebra index definitions in a package conversion #4

Open wizzyrea opened 11 years ago

wizzyrea commented 11 years ago

in a regular dev install, the Koha zebra definitions are kept in (for example) ~/koha-dev with the rest of the /etc type stuff.

With a package install, it's fine to keep the koha-conf in it's original location, but the zebra definitons are kept in /etc/koha/zebradb, and if we update a gitified install, those zebra definitions won't keep pace with git. For what it's worth, this is an issue with a regular git install as well - the solution for a regular git install is to symlink the things in ~/koha-dev/etc/zebradb to ~/kohaclone/etc/zebradb - it could be the same for a gitified package install - symlink the /etc/koha/zebradb to ~/kohaclone/etc/zebradb, so that when a git install is updated and reindexed using the package tools, the zebra definitions used will always be the newest ones.

bartonski commented 9 years ago

Note that the paths to the zebra files for biblios are actually in zebra-biblios-dom.cfg. This means that a gitified instance could have its own koha-conf.xml, pointed to by $KOHA_CONF, this would, in turn point to a custom zebra-biblios-dom.cfg with profilePath set to point to the correct place in kohaclone.

Presumably, authorities would be handled similarly.

mrenvoize commented 9 years ago

See also bug 12216 on bugzilla. http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12216

Really, zebra config files are just that.. config files. They should allow for customisations and therefore not get replaced by upgrades. This is a bit of a bug with the packages in general at the moment.

However, with a git install done right, then when you update your git repository you should really be following that by the usual 'make && make upgrade' routine at which point the upgraded defaults in the git repository will be copied accross to koha-dev/etc/whatever and a backup made of the originals. That way one can then compare the new with the old and port across any customisations.

I'm not sure how best to handle this with either the packages or gitified.. but it's certainly worth drawing peoples attention to it.