Debian¶

Stable Version¶

To get the stable 3.8 release, add this to a /etc/apt/sources.list.d/koha.list file:

deb http://debian.koha-community.org/koha squeeze main

Old Stable Version¶

To get the old stable 3.6 release, add this to a /etc/apt/sources.list.d/koha.list file:

deb http://debian.koha-community.org/koha oldstable main

Development Version¶

To get the development release (currently from 3.9), add this to your /etc/apt/sources.list.d/koha.list file:

deb http://debian.koha-community.org/koha squeeze-dev main

Everyone¶

Add the key in gpg.asc to your APT trusted keys:

wget -O- http://debian.koha-community.org/koha/gpg.asc | sudo apt-key add -

(If you are familiar with GnuPG, you will want to verify that you have a trust path to the key. If you do not know how to do that, this space is unfortunately too limited to explain how and you will have to take your chances.)

After that, you should be able to install Koha:

apt-get update
apt-get install koha-common (!! see below !!)
less /usr/share/doc/koha-common/README.Debian  (!! or less /usr/share/doc/koha/README.Debian !!)

Read the README.Debian file for instructions on how to configure Koha after the package is installed.

Wait! There are actually two packages here: koha and koha-common.

• koha-common contains all the code and support scripts. It won’t give you a koha instance that is up and running on installation, but it does allow you to use koha-create and associated tools to create as many instances as you want. Anything created with this command will automatically be managed by cron jobs, and zebra will work, and so forth.
• koha is similar, but provides a single site. At the moment however, this site can’t be managed by the tools that come with the package, and so you will need to set up the cron jobs and zebra for it yourself. See bug 5071 for plans to fix this. It is not recommend that you use this package yet.

Initial Configuration¶

This assumes that you are using the koha-common package.

To configure your server for use with DNS names: After install, edit /etc/koha/koha-sites.conf with details about your site. You may need to create this file. Some example content would be:

DOMAIN=".mydomain.co.nz"  # Any library instance will be a subdomain of this string.
INTRAPORT="80"  # TCP listening port for the administration interface
INTRAPREFIX=""  # For administration interface URL: Prefix to be added to the instance name.
INTRASUFFIX="-intra"  # For administration interface URL: Suffix to be added to the instance name.
DEFAULTSQL="/usr/share/koha/defaults.sql.gz"  # only needed if you're pre-populating from another Koha database
OPACPORT="80"  # TCP listening port for the users' interface (if you skip this, the apache default of 80 will be used)
OPACPREFIX=""  # For users' interface URL: Prefix to be added to the instance name.
OPACSUFFIX=""  # For users' interface URL: Suffix to be added to the instance name.
ZEBRA_MARC_FORMAT="marc21"  # Specifies format of MARC records to be indexed by Zebra. Possible values are 'marc21', 'normarc' and 'unimarc'
ZEBRA_LANGUAGE="en"  # Primary language for Zebra indexing. Possible values are 'en', 'fr' and 'nb'

Next, you will need to enable the Apache mod_rewrite module:

sudo a2enmod rewrite

If you are planning to run MySQL on the same server as you are running Koha on, then make sure you install it:

sudo apt-get install mysql-server

If you’re planning to run MySQL on a separate server, please do not run ``koha-create –create-db ````instancename`` as mentioned below. Instead, see Install Koha 3.6 on Debian squeeze using a separate MySQL server.

Creating the Koha Instance¶

Now you need to create your first koha instance. Replace instancename with the name of your library. If you want to have library.example.com, then instancename can probably be “library”.

sudo koha-create --create-db instancename

Now you can visit your admininstration website to continue with the Koha web installer.

The username to log in with will be koha_``instancename`` and the password will be near the end of /etc/koha/sites/``instancename``/koha-conf.xml. You will need to be root to view this You could also use this command:

sudo xmlstarlet sel -t -v 'yazgfs/config/pass' /etc/koha/sites/instancename/koha-conf.xml

to print it out.

Building Languages¶

Commands to build a language for interface (example for france french):

/usr/share/koha/misc/translator
sudo env PERL5LIB=/usr/share/koha/lib/ KOHA_CONF=/etc/koha/sites/instancename/koha-conf.xml perl translate install fr-FR

Commands to build all available languages for interface:

/usr/share/koha/misc/translator
Langs="$(ls -1 /usr/share/koha/misc/translator/po/ | grep -ie "pref.po" | sed -e "s/-pref\.po//g")"
for Current in $Langs ; do sudo env PERL5LIB=/usr/share/koha/lib/ KOHA_CONF=/etc/koha/sites/instancename/koha-conf.xml perl translate install $Current ; done

koha-common installs a number of handy commands, which are still somewhat underdocumented. Here is an overview of these:

• koha-create: create a new library instance. For example koha-create --create-db mylibrary will create a new koha catalogue called ‘mylibrary’, create and populate the database for it, set up zebra, and configure Apache appropriately. Note that by default after creation, your Koha instance may be disabled. If you get “command not found”, try /usr/sbin/koha-create (It’s possible that that isn’t on your $PATH).
  • There are a number of options to ``koha-create` <http://wiki.koha-community.org/w/index.php?title=Commands_provided_by_the_Debian_packages%23koha-create>`_ that allow you do to things such as set your MARC flavour and language for zebra.
• koha-enable/koha-disable: this lets you enable or disable a Koha instance, e.g. koha-enable.
• koha-email-enable/koha-disable-email: turn on or off sending of email for the Koha instance. If email is disabled, the mail queue is regularly cleared in order to prevent a wave of emails when its turned on. Note: by default, a new Koha instance has the mail disabled.
• koha-remove: deletes a Koha instance

See also: Commands provided by the Debian packages.