The following assumes that
The whole process of making Koha work on Caudium/Roxen can be described in 4 (very large) steps:
Steps 3 and 4 are mostly identical and will be described in detail below.
If you have control over your DNS zone files, it may be more convenient to create separate host names for the OPAC and the Intranet. In that case, you might want to use the “Virtual host matcher” module. (The “IP-less virtual hosting” module also works, and is much more intuitive to set up; but unfortunately it is deprecated.)
Just use the adduser command to create a user to run koha. On most GNU/Linux distributions, “adduser koha” will do.
koha
: This should be the same user that will run the Koha CGI scripts within the CGI Support module in your Koha virtual servers.The steps for creating a virtual server for both the OPAC and INTRANET are mostly identical. For the purpose of illustrating, the steps for creating a virtual server for OPAC will be shown below.
To create the virtual server for INTRANET, replace opac
(the word “opac” in italics) below with intranet
.
opac
/cgi-binopac
/htdocsYour virtual server should now be ready.
You might want to disable RXML parsing for this virtual server, since this functionality is not needed for Koha.
You might want to add a new Filesystem module mounted on /opac
-tmpl and leave the search path at NONE (or some empty directory).