We are trying to fully understand how to make multiple interfaces for the same Koha instance in order to have OPAC setups for a main site and a branch site. We found this post in the wiki: https://wiki.koha-community.org/wiki/Support_for_multiple_PAC_interfaces_by_... and I see these lines in the koha httpd configuration file: # Repeat this virtualhost stanza changing the following environment vars to # create multiple OPAC interfaces with custom css and/or search limits: # SetEnv OPAC_CSS_OVERRIDE mystyle.css # SetEnv OPAC_SEARCH_LIMIT branch:CODE # SetEnv OPAC_LIMIT_OVERRIDE 1 but it is not fully clear how this all works. Do we have to create two different virtual hosts with IP aliases? How much of the Apache configuration needs to be repeated to get this all working? If someone who has done this can give me some more concrete and complete examples of this, with information on what changes need to be made within Koha as well as example httpd configuration, that would really help. Or maybe there is additional documentation somewhere that is more complete? Thanks in advance, Tom Hanstra -- *Tom Hanstra* *Sr. Systems Administrator* hanstra@nd.edu <http://library.nd.edu/>
Hi, On Wed, Jul 27, 2016 at 9:30 AM, Tom Hanstra <hanstra@nd.edu> wrote:
# Repeat this virtualhost stanza changing the following environment vars to # create multiple OPAC interfaces with custom css and/or search limits: # SetEnv OPAC_CSS_OVERRIDE mystyle.css # SetEnv OPAC_SEARCH_LIMIT branch:CODE # SetEnv OPAC_LIMIT_OVERRIDE 1
but it is not fully clear how this all works. Do we have to create two different virtual hosts with IP aliases? How much of the Apache configuration needs to be repeated to get this all working?
Assuming that you are using different names to distinguish between the interfaces (e.g., foo.library.nd.edu, bar.library.nd.edu, etc.), the Apache config should have a copy of the entire OPAC VirtualHost section for each entry point; the differences between each one would consist of: - ServerName (and/or ServerAliases) - SetEnv OPAC_CSS_OVERRIDE, etc. - SSLCertificateFile (unless you're pointing them all at the same wildcard certificate) Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Software, Inc. / Open Your Library email: gmc@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org
Can OPAC_CSS_OVERRIDE reference an external CSS file, or does it have to reside on the Koha server? On 7/27/2016 1:48 PM, Galen Charlton wrote:
Hi,
On Wed, Jul 27, 2016 at 9:30 AM, Tom Hanstra <hanstra@nd.edu> wrote:
# Repeat this virtualhost stanza changing the following environment vars to # create multiple OPAC interfaces with custom css and/or search limits: # SetEnv OPAC_CSS_OVERRIDE mystyle.css # SetEnv OPAC_SEARCH_LIMIT branch:CODE # SetEnv OPAC_LIMIT_OVERRIDE 1
but it is not fully clear how this all works. Do we have to create two different virtual hosts with IP aliases? How much of the Apache configuration needs to be repeated to get this all working?
Assuming that you are using different names to distinguish between the interfaces (e.g., foo.library.nd.edu, bar.library.nd.edu, etc.), the Apache config should have a copy of the entire OPAC VirtualHost section for each entry point; the differences between each one would consist of:
- ServerName (and/or ServerAliases) - SetEnv OPAC_CSS_OVERRIDE, etc. - SSLCertificateFile (unless you're pointing them all at the same wildcard certificate)
Regards,
Galen
-- Andy Boze, Associate Librarian University of Notre Dame 208A Hesburgh Library (574) 631-8708
participants (3)
-
Andy Boze -
Galen Charlton -
Tom Hanstra