On Mon, Jul 27, 2009 at 2:32 PM, Michael Hafen <mdhafen@tech.washk12.org> wrote:
On Mon, 2009-07-27 at 20:18 +0200, Sébastien Hinderer wrote:
> Hi,
>
> > I am doing named virtual hosting and it turned out to be a lot easier
> > than I thought it would be. Two databases, two koha installs, two
> > koha.conf files.
>
> Unless one Koha is used for development whereas the other one is
> expected to be stable, I don't think it is necessary to have wto
> instances of the whole code. One install plus two databases and two
> configuration files shoulc be enough, the apache stuff put aside.

I'm wondering how this applies to the Zebra config files.  There are
several zebra files that have directory paths which would have to be
different for the two Koha installs.

It would be easy enough to have modified copies of these files, and
point one of the koha-conf.xml files at the copies.  Just wanted to
mention this caveat.

You can just do the command-line installation twice, and give it different configuration directories ("~/koha-dev" vs. '"~/koha-pro" or whatever).  All the zebra and other config files will live in there for their respective installations.  These are outside the codebase repository. 

You could have an arbitrary number of DBs running on the same code, but you will have to get remember to update each at updatedatabase time.

--
Joe Atzberger
LibLime - Open Source Library Solutions