Hi Quoc Uy,
I've got a feeling your misunderstanding the virtual hosts set-up that
Jonathan and Liz are talking about. In the setup described you are using
one koha install with on database and one staff client. The big difference
is that your using multiple OPAC's for that single koha instance
To Liz and Jonathan: What you two said is similar:
http://wiki.koha-community.org/wiki/Support_for_multiple_PAC_interfaces_by_URL_RFC
I'm not sure about what you are talking is about independent branches or
separated instances. Now we can create a lot of instances with only one Koha
installation
I've had a play with this in the past and it works nicely. You just
add the config options to your VirtualHost in Apache
SetEnvIf Host "demo1.xxx.xxx.xxx" OPAC_CSS_OVERRIDE=opac-main.css OPAC_SEARCH_
LIMIT=branch:MAIN OPAC_LIMIT_OVERRIDE=1
SetEnvIf Host "demo2.xxx.xxx.xxx" OPAC_CSS_OVERRIDE=opac-b
Actually, upon further review I find that this work *was* done, and you
can simply create multiple virtualhosts, each with a unique URL, and
specify a CSS file to use for each one. Details can be found in the
koha-httpd.conf file.
Liz Rea
On 04/01/13 12:17, Liz Rea wrote:
I think what you wan
I think what you want is not entirely impossible, but I can say that it
would likely be a lot of work to maintain.
A few years ago we had a RFC for the following work, which was never
done but I think would do something similar to what you are describing,
and possibly be easier to maintain thr
My idea comes from creating 1 Koha installed with 1 Database for 100
small branches libraries. Each branch has separated template OPAC. There
should be a folder in koha and logic in the application that saying ... ok,
load branchA's template OPAC for BranchA's user when they login. A
