ANNOUNCE: New Installer in master git tree
Well, one koha user already tried it, so I guess I should announce it here: THE NEW INSTALLER IS IN THE MASTER TREE The new installer is based on MakeMaker, the tool that is usually used to install CPAN modules. This means that if you know how to customise CPAN-installed modules, the same things should work for you with Koha. If not, don't worry. If you want to customise the installation more than described in the README.txt, run "man ExtUtils::MakeMaker" By default, the installer doesn't ask you any questions and tries to assume sane defaults, which I think is A Good Thing, but you can override most of the settings with environment variables. For instructions on how, run perldoc rewrite-config.PL As well as the CPAN-package-style installation, there is also a very quick-and-dirty script called install-CPAN.pl which should install all dependencies from CPAN automatically. For instructions on how to package releases, run perldoc Makefile.PL TREE STRUCTURE C4/*.pm is copied to perl’s lib namespace. CGIs are copied to $(PREFIX)/lib/cgi−bin/koha/ and other scripts to koha/ in perl's lib. Config files are copied to $(PREFIX)/share/koha/etc Templates are copied to koha/templates, excluding non−files, CVS files and whitespace in filenames. KNOWN BUGS There is no zebra init script and some of the zebra-related directories are not constructed and not complete. This is partly because I don't really know what I'm doing with the zebra server yet. Can anyone explain it to me, or remind me where to find the explanation, please? Thanks, -- MJ Ray - see/vidu http://mjr.towers.org.uk/email.html Experienced webmaster-developers for hire http://www.ttllp.co.uk/ Also: statistician, sysadmin, online shop builder, workers co-op. Writing on koha, debian, sat TV, Kewstoke http://mjr.towers.org.uk/
MJ Ray a écrit :
Well, one koha user already tried it, so I guess I should announce it here:
THE NEW INSTALLER IS IN THE MASTER TREE
Hi MJ, I tried your installer and have some questions/suggestions : - how to define the directory where I want to install Koha ? - how to define login/password for mySQL ? (same question for zebra) Atm, it seems to be defaulted to kohaadmin / katikoan, which is a MAJOR security flaw : I bet that 90% of the setups will be done without changing it, thus anyone can connect to librarian interface as superlibrarian without any problem ! I think we must at least ask for a login/password (something like : perl Makefile.PL --login=XXX --password=YYY, otherwise, die with a message. - I think the installer don't create the mySQL login (kohaadmin / katikoan by default), it can't as the root password is unknown from the installer. What about adding a --master-login --master-password parameter to add the login/password in mySQL ? If we don't do it automatically, we should at least warn the users that it's not done ;-) Note that the webinstaller requires the koha login/password, and only that. HTH -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19
Paul POULAIN <paul.poulain@free.fr> wrote:
- how to define the directory where I want to install Koha ?
Set PREFIX and CGI_DIR environment variables, but the File Hierarchy Standard defaults should be good for most people. See perldoc rewrite-config.PL for a full list of what you can change.
- how to define login/password for mySQL ? (same question for zebra)
Set the MYSQL_DB, MYSQL_HOST, MYSQL_PASS, MYSQL_USER environment variables. Maybe I should mention these in README.txt and randomise an unset MYSQL_PASS instead of using katikoan. The installer does not yet configure zebra. See the KNOWN BUGS bit of my announcement. That is the next-but-one thing on my TODO. While you can tell koha the MySQL connection details, actually creating the MySQL login and DB will be left to the sysadmin. This is because there's just too much variety between different distributions and hosting control panels on the "correct" way to do it. I believe that's why the mysql step of 2.x installer broke so often. I'm quite happy to include a setup-mysql.sh script in the distribution, but I think it needs to be its own step. If someone would like to prove me wrong now and tell me one way that will work for all platforms, go for it ;-) [...]
Note that the webinstaller requires the koha login/password, and only that.
Could the web installer ask for (but not store) the mysql admin login/password and create the koha login/password if it doesn't work yet? Thanks, -- MJ Ray http://mjr.towers.org.uk/email.html tel:+844-4437-237 - Webmaster-developer, statistician, sysadmin, online shop builder, consumer and workers co-operative member http://www.ttllp.co.uk/ - Writing on koha, debian, sat TV, Kewstoke http://mjr.towers.org.uk/
MJ Ray a écrit :
Paul POULAIN <paul.poulain@free.fr> wrote:
- how to define the directory where I want to install Koha ?
Set PREFIX and CGI_DIR environment variables, but the File Hierarchy Standard defaults should be good for most people. See perldoc rewrite-config.PL for a full list of what you can change.
something to add in README.txt
- how to define login/password for mySQL ? (same question for zebra)
Set the MYSQL_DB, MYSQL_HOST, MYSQL_PASS, MYSQL_USER environment variables. Maybe I should mention these in README.txt and randomise an unset MYSQL_PASS instead of using katikoan.
The installer does not yet configure zebra. See the KNOWN BUGS bit of my announcement. That is the next-but-one thing on my TODO.
I think that the install setup should be : - install Koha, apache part - run webinstaller for librarian questions - at the end of the webinstaller, ask "are you a large library, that will run zebra, or a small one that will run Koha 3.0 without zebra" (explain what it means exactly here) If the user choose "NoZebra" => set the systempref accordingly If the user choose "Zebra" => just say "ok guy, you'll have to ask your sysadm to install zebra, say him to look at wiki.koha.org/blabla Note that you won't be able to search in your catalogue until he has done the stuff. Other functions are running immediatly" Then the sysadm runs what is needed to run zebra. I can't imagine even a second that setting zebra can be done through a script. rebuild_zebra.pl will do most of the stuff, but the library will have to set zebra as a service, and that's different on every system (Linux, Unix, Mac OSX, Windows) Plus Zebra is for large libraries, with a sysadm, so it's not a problem for me. If I were a sysadm, I would be happier to have some doc than a script that need to be root & run I don't know what...
While you can tell koha the MySQL connection details, actually creating the MySQL login and DB will be left to the sysadmin. This is because there's just too much variety between different distributions and hosting control panels on the "correct" way to do it. I believe that's why the mysql step of 2.x installer broke so often. I'm quite happy to include a setup-mysql.sh script in the distribution, but I think it needs to be its own step.
agree.
If someone would like to prove me wrong now and tell me one way that will work for all platforms, go for it ;-)
I have the same feeling ;-)
[...]
Note that the webinstaller requires the koha login/password, and only that.
Could the web installer ask for (but not store) the mysql admin login/password and create the koha login/password if it doesn't work yet?
It could, but it would need a root/login access, that can't be required because the main idea of the web installer is to have something for the *librarian* And I can't imagine a sysadmin giving a root access to a librarian ;-) So the idea to have a small script is the best direction to go imho. -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19
MJ Ray a écrit :
Paul POULAIN <paul.poulain@free.fr> wrote:
- how to define the directory where I want to install Koha ?
Set PREFIX and CGI_DIR environment variables, but the File Hierarchy Standard defaults should be good for most people. See perldoc rewrite-config.PL for a full list of what you can change.
something to add in README.txt
- how to define login/password for mySQL ? (same question for zebra)
Set the MYSQL_DB, MYSQL_HOST, MYSQL_PASS, MYSQL_USER environment variables. Maybe I should mention these in README.txt and randomise an unset MYSQL_PASS instead of using katikoan.
The installer does not yet configure zebra. See the KNOWN BUGS bit of my announcement. That is the next-but-one thing on my TODO.
I think that the install setup should be : - install Koha, apache part - run webinstaller for librarian questions - at the end of the webinstaller, ask "are you a large library, that will run zebra, or a small one that will run Koha 3.0 without zebra" (explain what it means exactly here) If the user choose "NoZebra" => set the systempref accordingly If the user choose "Zebra" => just say "ok guy, you'll have to ask your sysadm to install zebra, say him to look at wiki.koha.org/blabla
Note that you won't be able to search in your catalogue until he has done the stuff. Other functions are running immediatly"
Then the sysadm runs what is needed to run zebra. I can't imagine even a second that setting zebra can be done through a script. Most of Zebra's configuration can now be set up using a set of standard conventions, I don't think we should just relegate that setup to the local sysadmin, it's too complicated a process. We need to provide them with some sound defaults IMO. For instance, I think official Koha 3.0 should have both global and database-specific configuration files, probably
rebuild_zebra.pl will do most of the stuff, but the library will have to set zebra as a service, and that's different on every system (Linux, Unix, Mac OSX, Windows) Plus Zebra is for large libraries, with a sysadm, so it's not a problem for me. If I were a sysadm, I would be happier to have some doc than a script that need to be root & run I don't know what... I think we definitely want to provide documentation, but I also think
----- "Paul POULAIN" <paul.poulain@free.fr> wrote: the following: global: default.idx explain.att gils.att numeric.chr tagsetm.tag word-phrase-utf.chr explain.abs explain.tag kohalis sort-string-utf.chr usmarc.mar database-specific: bib1.att record.abs Of these, the only one that MUST be configured for each system is kohalis, that stores the Zebra authentication info. that if Zebra's too hard to use, users won't bother. Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf@liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS
While you can tell koha the MySQL connection details, actually creating the MySQL login and DB will be left to the sysadmin. This is because there's just too much variety between different distributions and hosting control panels on the "correct" way to do it. I believe that's why the mysql step of 2.x installer broke so often. I'm quite happy to include a setup-mysql.sh script in the distribution, but I think it needs to be its own step.
agree.
If someone would like to prove me wrong now and tell me one way that will work for all platforms, go for it ;-)
I have the same feeling ;-)
[...]
Note that the webinstaller requires the koha login/password, and only that.
Could the web installer ask for (but not store) the mysql admin login/password and create the koha login/password if it doesn't work yet?
It could, but it would need a root/login access, that can't be required because the main idea of the web installer is to have something for the *librarian* And I can't imagine a sysadmin giving a root access to a librarian ;-)
So the idea to have a small script is the best direction to go imho.
-- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19
_______________________________________________ Koha-devel mailing list Koha-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-devel
Paul POULAIN <paul.poulain@free.fr> wrote:
MJ Ray a écrit :
The installer does not yet configure zebra. See the KNOWN BUGS bit of my announcement. That is the next-but-one thing on my TODO.
I think that the install setup should be : - install Koha, apache part - run webinstaller for librarian questions - at the end of the webinstaller, ask "are you a large library, that will run zebra, or a small one that will run Koha 3.0 without zebra" (explain what it means exactly here)
Here's where I'm confused: I thought that Zebra was the best thing since sliced bread and anyone who has enough server permissions to use it should be using it, because Koha-Z is faster than Koha-NZ on the same server. Is it?
If the user choose "NoZebra" => set the systempref accordingly If the user choose "Zebra" => just say "ok guy, you'll have to ask your sysadm to install zebra, say him to look at wiki.koha.org/blabla Note that you won't be able to search in your catalogue until he has done the stuff. Other functions are running immediatly" Then the sysadm runs what is needed to run zebra. I can't imagine even a second that setting zebra can be done through a script.
While some koha sysadmins will probably want to tweak Zebra, can't we ship a generally-useful default? What's the complication?
rebuild_zebra.pl will do most of the stuff, but the library will have to set zebra as a service, and that's different on every system (Linux, Unix, Mac OSX, Windows)
What does this do (misc/migration_tools/rebuild_zebra.pl has no perldoc) and should we call it from some CGI (the web installer?) if required? I'll add a note to README.txt about the zebra service. "Joshua M. Ferraro" <jmf@liblime.com> wrote:
Most of Zebra's configuration can now be set up using a set of standard conventions, I don't think we should just relegate that setup to the local sysadmin, it's too complicated a process. We need to provide them with some sound defaults IMO. For instance, I think official Koha 3.0 should have both global and database-specific configuration files, probably the following:
global: default.idx explain.att gils.att numeric.chr tagsetm.tag word-phrase-utf.chr explain.abs explain.tag kohalis sort-string-utf.chr usmarc.mar
database-specific: bib1.att record.abs
I think have added all of these and some more from zoom_basic to koha.git - I'll post patches shortly. Please fix as needed. I also see usmarc.mar there - what about other MARC flavours?
Of these, the only one that MUST be configured for each system is kohalis, that stores the Zebra authentication info.
I also need to update koha-conf.xml and the zebra-*.cfg files with system configuration details. Anything else? Thanks, -- MJ Ray http://mjr.towers.org.uk/email.html tel:+44-844-4437-237 - Webmaster-developer, statistician, sysadmin, online shop builder, consumer and workers co-operative member http://www.ttllp.co.uk/ - Writing on koha, debian, sat TV, Kewstoke http://mjr.towers.org.uk/
Hey MJ ... just testing the new installer a bit and I've got a couple questions: rewrite-config.PL doesn't seem to do anything, could you explain how it works? I'd like to change the prefix to /home/jmf/koha when I do 'make' I get an error: mkdir /usr/lib/cgi-bin/koha: Permission denied at /usr/share/perl/5.8/ExtUtils/Install.pm line 443 make: *** [pm_to_blib] Error 13 My understanding of how make works is that it compiles in the current dir, and make install is what moves the files into their final directories ... of course, I could be wrong ... let me know. Thanks, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf@liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS ----- "MJ Ray" <mjr@phonecoop.coop> wrote:
Paul POULAIN <paul.poulain@free.fr> wrote:
MJ Ray a écrit :
The installer does not yet configure zebra. See the KNOWN BUGS bit of my announcement. That is the next-but-one thing on my TODO.
I think that the install setup should be : - install Koha, apache part - run webinstaller for librarian questions - at the end of the webinstaller, ask "are you a large library, that
will run zebra, or a small one that will run Koha 3.0 without zebra"
(explain what it means exactly here)
Here's where I'm confused: I thought that Zebra was the best thing since sliced bread and anyone who has enough server permissions to use it should be using it, because Koha-Z is faster than Koha-NZ on the same server. Is it?
If the user choose "NoZebra" => set the systempref accordingly If the user choose "Zebra" => just say "ok guy, you'll have to ask
your sysadm to install zebra, say him to look at wiki.koha.org/blabla Note that you won't be able to search in your catalogue until he has
done the stuff. Other functions are running immediatly" Then the sysadm runs what is needed to run zebra. I can't imagine even a second that setting zebra can be done through a script.
While some koha sysadmins will probably want to tweak Zebra, can't we ship a generally-useful default? What's the complication?
rebuild_zebra.pl will do most of the stuff, but the library will have to set zebra as a service, and that's different on every system (Linux,
Unix, Mac OSX, Windows)
What does this do (misc/migration_tools/rebuild_zebra.pl has no perldoc) and should we call it from some CGI (the web installer?) if required?
I'll add a note to README.txt about the zebra service.
Most of Zebra's configuration can now be set up using a set of standard conventions, I don't think we should just relegate that setup to
local sysadmin, it's too complicated a process. We need to provide
with some sound defaults IMO. For instance, I think official Koha 3.0 should have both global and database-specific configuration files,
"Joshua M. Ferraro" <jmf@liblime.com> wrote: the them probably
the following:
global: default.idx explain.att gils.att numeric.chr tagsetm.tag word-phrase-utf.chr explain.abs explain.tag kohalis sort-string-utf.chr usmarc.mar
database-specific: bib1.att record.abs
I think have added all of these and some more from zoom_basic to koha.git - I'll post patches shortly. Please fix as needed. I also see usmarc.mar there - what about other MARC flavours?
Of these, the only one that MUST be configured for each system is kohalis, that stores the Zebra authentication info.
I also need to update koha-conf.xml and the zebra-*.cfg files with system configuration details. Anything else?
Thanks, -- MJ Ray http://mjr.towers.org.uk/email.html tel:+44-844-4437-237 - Webmaster-developer, statistician, sysadmin, online shop builder, consumer and workers co-operative member http://www.ttllp.co.uk/ - Writing on koha, debian, sat TV, Kewstoke http://mjr.towers.org.uk/
Paul POULAIN <paul.poulain@free.fr> wrote:
MJ Ray a écrit :
Paul POULAIN <paul.poulain@free.fr> wrote:
- how to define the directory where I want to install Koha ?
Set PREFIX and CGI_DIR environment variables, but the File Hierarchy Standard defaults should be good for most people. See perldoc rewrite-config.PL for a full list of what you can change.
something to add in README.txt
OK, I am doing this. Will post patches soon.
[...]
Note that the webinstaller requires the koha login/password, and only that.
Could the web installer ask for (but not store) the mysql admin login/password and create the koha login/password if it doesn't work yet?
It could, but it would need a root/login access, that can't be required because the main idea of the web installer is to have something for the *librarian* And I can't imagine a sysadmin giving a root access to a librarian ;-)
So the idea to have a small script is the best direction to go imho.
I doubt it will be used very often, but there are small-library librarians who are their own sysadmins and they do have root access to mysql, but aren't comfortable using the mysql command line. But, I suspect this would cause other complications with the config files needing to be edited after the installer has finished, so it's probably simplest to leave it out and to add a small setup-mysql-koha script soon. Regards, -- MJ Ray http://mjr.towers.org.uk/email.html tel:+44-844-4437-237 - Webmaster-developer, statistician, sysadmin, online shop builder, consumer and workers co-operative member http://www.ttllp.co.uk/ - Writing on koha, debian, sat TV, Kewstoke http://mjr.towers.org.uk/
participants (3)
-
Joshua M. Ferraro -
MJ Ray -
Paul POULAIN