Skip to content

Deal with zebra index definitions in a package conversion #4

@wizzyrea

Description

@wizzyrea

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.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions