Hello. I installed koha 2.0.0 about a month ago, and wrote down some info about my experiences with it afterward. I began the process as a complete koha newbie, though I've been a *nix sysadmin for nearly a decade. Anyway, I'm providing these notes in hopes it will help the koha developers: Installation experiences... I went to koha's main site and found a download link to sourceforge. Continuing, I found a tarball for koha-2.0.0, and grabbed it. After unpacking, I browsed the contents a bit. The README had very little info, and said to run the installer. No INSTALL file was provided. I don't like running downloaded executables on my system; who knows what they might do? Such a script might assume things which are not true about me, or my system. I probably didn't even have its dependencies satisfied, so I decided to get more information first. Suggestion: Create an INSTALL file, and list all dependencies in it. Also, describe what the installer script does, in detail. I looked at the koha site again, for installation info. It had a decent installation guide, here: http://www.koha.org/installation/quick-start.html I read the hints there, the faq, and the install guide. I located the debian packages for listed dependencies, and installed them. I got the rest of the deps from cpan, packaged them into .deb files, and installed them. Then I followed directions, and ended up without a working koha. This was partly because of a typo in apache's config, but mostly because I had tried to do as the install guide said. Suggestion: update the online docs to reflect the current version. Perhaps maintain them along with the koha source, and copy the files to the site whenever there is a new release. Or, at least, add a note to the online docs stating they do not apply to koha 2.0.0 or newer. Eventually, I decided to run the installer, as a throwaway user, to see what it did. It informed me about additional dependencies, so I located and/or built those again, as needed. Continuing on, I learned all about what the installer does, but it failed to set up the database correctly. I got enough errors that I couldn't scroll back to see where they started. ... I have a pretty long scrollback buffer. Anyway, the installer continued merrily along, having noticed nothing wrong. Suggestion: check for errors during installer operations. Other than the database errors, and the expected failure while trying to write to /etc, all went well. I decided to run it as root as soon as I got the database problem fixed. But, as it turns out, running as non-root was the problem. I discovered this after I found the koha IRC channel and chris helped me. (thanks!) It gets DB info from /etc instead of from the installer script, so failing to write /etc/koha.conf is fatal to the install. Suggestion: list the IRC channel somewhere on the main site; it was buried near the last hit on google. Suggestion: notify user that installer must be run as root. Or, add non-root installation capability. Or, abort install when writing to /etc fails, and explain why to the user. Continuing, I ran the installer as root, and it worked. It still printed a bunch of red text during the database portion, but none of it was errors. I then looked at the apache config it generated, merged parts into my apache config, and tested. On the first try, it failed, but then I fixed a typo from earlier, and it worked. :) -- Scott
Scott, Thanks for your testing. I'll probably add most of the things you mention to the bugs.koha.org if they're not already there. I find the outdated docs on the koha.org site cause more people problems than almost anything else. I will update the docs in the tarball before 2.0.1 is released, hopefully next week. On 2004-07-01 23:16:24 +0100 Scott Scriven <koha-main@toykeeper.net> wrote:
Suggestion: notify user that installer must be run as root. Or, add non-root installation capability. Or, abort install when writing to /etc fails, and explain why to the user.
There is non-root installation capability through prefix and etcdir environment variables. That was one of the first things I added. I should probably bomb out if we can't write to the chosen etcdir (which defaults to "/etc"). -- MJR/slef My Opinion Only and not of any group I know http://www.ttllp.co.uk/ for creative copyleft computing "To be English is not to be baneful / To be standing by the flag not feeling shameful / Racist or partial..." (Morrissey)
Bug numbers refer to bugs.koha.org On 2004-07-01 23:16:24 +0100 Scott Scriven <koha-main@toykeeper.net> wrote:
Suggestion: Create an INSTALL file, and list all dependencies in it. Also, describe what the installer script does, in detail.
Bug 65.
[...] add a note to the online docs stating they do not apply to koha 2.0.0 or newer.
Bug 620.
Suggestion: check for errors during installer operations.
I try. If you can narrow down the particular uncaught error, I'll try to catch it.
Suggestion: list the IRC channel somewhere on the main site; it was buried near the last hit on google.
It's on http://www.koha.org/about/ -- where else would you like it?
Suggestion: notify user that installer must be run as root. Or, add non-root installation capability. Or, abort install when writing to /etc fails, and explain why to the user.
It notifies the user in the opening "Welcome to the Koha installer" message. I'll improve the wording. I agree that it should check that it can write to /etc, so I've added a check which will appear in 2.0.1. -- MJR/slef My Opinion Only and not of any group I know http://www.ttllp.co.uk/ for creative copyleft computing "To be English is not to be baneful / To be standing by the flag not feeling shameful / Racist or partial..." (Morrissey)
participants (2)
-
MJ Ray -
Scott Scriven