User manual

Chapter 2
Configuration prerequisites
Here is a list of prerequisites that you might want to take care of; some of these may
not apply to your situation depending on the sort of configuration plan you have.
Item
Description
Open Firewall ports
Host Names
Domain Name Service (DNS)
IP Addresses
If you are using ports other port 80, you might
need to open those ports on network firewalls or
routers.
If you intend to use host names, you will have to
purchase or set them up.
If you use host names,
you will
have to set them up
in a DNS to route requests to the Koha server.
If you are using IP based virtual hosts, you will
need to ensure network cards are installed on your
server.
Configuring Apache2 web
server
Now that we have our configuration plan in place, let us get started with Apache2
configuration. We will edit the OPAC and staff client virtual hosts in Koha's Apache2
configuration file. We will also configure Apache2 to listen on the staff client port -
8080 and we will enable its Rewrite module. To make all this work we will point
Apache2 to Koha's Apache2 configuration file using a symbolic link.
Creating a symbolic link to koha -httpd.conf
1.
First we create a symbolic link in Apache2's virtual host's folder pointing to
Koha's Apache2 file. A symbolic link is just a pointer to the actual Koha file.
2.
We can copy the
koha -httpd. conf
file into the virtual host's folder, but it is
better to create a symbolic link as this helps when new versions of the file are
created during software upgrades.
3.
We use the In
command to create the symbolic link. The syntax is:
In -s <path to koha -httpd.conf> <path to symbolink link name>
4.
On Debian the command would be:
koha @1i190 -245:/$ sudo ln -s / home /koha /koha -dev /etc /koha -httpd.
conf / etc /apache2/ sites -available /koha -httpd.conf
5.
And on openSuSE, the command would look like this:
koha @1i190 -245:/$ sudo in -s /home /koha /koha -dev /etc /koha -httpd.
conf / etc / apache2 /vhosts.d /koha -httpd.conf
[31]