I am currently trying a first-time install of Koha (from latest CVS) on RedHat 6.2 As I proceed, I am trying to clarify and document problems that I encounter so although the stuff below is written in the style of statements, it is in fact questionable <grin> The starting point for this is the koha INSTALL document. I intend to expand on that and so, for that purpose, I have created a Koha installation wiki at: http://www.saas.nsw.edu.au/wiki/ It is also available for anyone to add/edit/modify via public Internet. The wiki content may eventually be a suitable update for the koha INSTALL file. The document is available now, but in order for me to proceed, can anyone please help clarify /correct the following: Koha is designed to be installed as two separate services - each having a unique web address and folder structure (two virtual web hosts). The folder structures for both servers are designed to operate separately and independently; The only reason for this is to simplify security setup? The "/cgi-bin/opac/*" scripts (placed in the opac cgi-bin folder) are a sub-set of the "/cgi-bin/koha/" scripts. To clarify this further: * The "/cgi-bin/opac/" cgi-bin folder contains _only_ those scripts in the root directory of the "scripts/" directory (found in the koha distribution). * The "koha" cgi-bin folder contains all files and folders found inside the distribution "scripts/" folder _except_ the "telnet" folder and non web stuff (see below). This means that the following sub folders and their contents... /scripts/acqui/*.pl /scripts/maint/*.pl /scripts/circ/*.pl /scripts/misc/*.pl /scripts/sec/*.pl ...should be copied to the root of /cgi-bin/koha/ (do not copy contents of telnet, tkperl, translator and updater directories to cgi-bin - see install manual for details). NOTE: Is there some way this could be implied? What about acqui.simple in CVS - does this mean either use /acqui/*.pl _or_ /acqui.simple/*.pl ? Both virtual hosts access a single database which may be on the same server or on a remote server. The two separate web servers are referred to as "koha" and "opac". The term "intranet" in the koha doc refers to the "koha" web site. NOTE: For consistency why not re-name the respective html distro folders koha-html and opac-html ? Catalogue maintenance and acquisitions links in /catalogue/index.html are broken (..."acquisitions/" link is relative instead of absolute... which (wrongly) requires that "acquisition" folder is a sub-folder of catalogue)? Also, I assume the "catmaintain.pl" should be located inside the "catalogue/" subdir - not the root of cgi-bin/koha/ ? Anyhow, I think the index.html links need to be tidied up ;^) I'm sure there is other stuff but I want to get feedback on above before going too far on a wild goose chase <grin> I'm happy to find, fix and diff anything obvious if that would help. In the meantime. I'll continue to provide more feedback/questions here. R.
Errata and expansion on previous message:
To clarify this further:
* The "/cgi-bin/opac/" cgi-bin folder contains _only_ those scripts in the root directory of the "scripts/" directory (found in the koha distribution).
* The "koha" cgi-bin folder contains all files and folders found inside the distribution "scripts/" folder _except_ the "telnet" folder and non web stuff (see below). This means that the following sub folders and their contents...
/scripts/acqui/*.pl /scripts/maint/*.pl /scripts/circ/*.pl /scripts/misc/*.pl /scripts/sec/*.pl
...should be copied to the root of /cgi-bin/koha/ (do not copy contents of telnet, tkperl, translator and updater directories to cgi-bin - see install manual for details).
NOTE: Is there some way this could be implied?
I meant: Is there some way this could be simplified? -----------------------------------------^^^^^^^^^^^ For example - Modify the directory layout to have /web-scripts/scripts/* and other-scripts/scripts/ which would include stuff like telnet etc? Or leave current distribution directory layout but have an Install.sh or example shell script command in the docs? R.
On Wed, 2002-03-20 at 12:38, Roger Buck wrote:
Errata and expansion on previous message:
...should be copied to the root of /cgi-bin/koha/ (do not copy contents of telnet, tkperl, translator and updater directories to cgi-bin - see install manual for details).
NOTE: Is there some way this could be implied?
I meant: Is there some way this could be simplified? -----------------------------------------^^^^^^^^^^^
For example - Modify the directory layout to have /web-scripts/scripts/* and other-scripts/scripts/ which would include stuff like telnet etc?
Hmmm yeah this makes sense, originally there was just the one dir, then came the maint dir, and acqui and circ etc. It would probably be easiest to just have /web-scripts/* and /other-scripts/* (Im assuming you mean in the released tarball or package not the cvs repository right?) Chris -- Chris Cormack Programmer 025 500 789 Katipo Communications Ltd chris@katipo.co.nz www.katipo.co.nz
Chris Cormack wrote: [--snip--]
For example - Modify the directory layout to have /web-scripts/scripts/* and other-scripts/scripts/ which would include stuff like telnet etc?
Hmmm yeah this makes sense, originally there was just the one dir, then came the maint dir, and acqui and circ etc.
It would probably be easiest to just have /web-scripts/* and /other-scripts/*
(Im assuming you mean in the released tarball or package not the cvs repository right?)
Your assumption is correct - cvs checkout structure remains unchanged. R.
Looks like Set::Scalar is required in addition to other perl modules currently listed in INSTALL ? R.
On Wed, 2002-03-20 at 14:31, Roger Buck wrote:
Looks like Set::Scalar is required in addition to other perl modules currently listed in INSTALL ? Hi Roger
Only for the version in cvs. And im not sure whether I like this or not yet. It certainly speeds up the keyword searches. But id like to do it another way. I have left all the original keyword search code in C4::Search, so it may well be that Set::Scalar disappears again before the next release. Chris -- Chris Cormack Programmer 025 500 789 Katipo Communications Ltd chris@katipo.co.nz www.katipo.co.nz
Chris Cormack wrote:
On Wed, 2002-03-20 at 14:31, Roger Buck wrote:
Looks like Set::Scalar is required in addition to other perl modules currently listed in INSTALL ? Hi Roger
Only for the version in cvs.
And im not sure whether I like this or not yet.
[--snip--] OK - All understood... I just like to get my test environments working properly if poss... that way I minimise the damage resulting from internal errors! :-) R.
Roger Buck wrote: Where are the "Exchange Rates" added/modified/set? No luck when I try to change values in "Acquisitions" (and no obvious error messages in httpd or mysql logs). R.
On Wed, 2002-03-20 at 18:02, Roger Buck wrote:
Roger Buck wrote:
Where are the "Exchange Rates" added/modified/set?
No luck when I try to change values in "Acquisitions" (and no obvious error messages in httpd or mysql logs).
Hmm It should just work from acquisitions It seems to from http://hlt.katipo.co.nz/acquisitions/ .. so perhaps theres a file thats missed a commit into cvs. Ill go check it out Chris -- Chris Cormack Programmer 025 500 789 Katipo Communications Ltd chris@katipo.co.nz www.katipo.co.nz
Suggestion: The navigation map (crc-crc.gif and related stuff) should be included by default in each koha (intranet) page header ? R.
Roger Buck wrote:
Suggestion:
The navigation map (crc-crc.gif and related stuff) should be included by default in each koha (intranet) page header ?
I have traced the source of this problem here. The page headers and footers are loaded as Server Side Includes from /pathtokoha/includes/*.inc AFAIC, for the headers and footers to be loaded from *.html files, Apache 1.2 and greater requires "XBitHack" parameter to be enabled in httpd.conf (may be different on other webservers). At http://www.saas.nsw.edu.au/wiki/ I have inluded an example block from httpd.conf with a link to relevant Apache docs. If the above is correct, then some koha *.html files will need to chmod 754 or 554 or 744 or 544 when copied to their web server. This may be another reason to include an install.sh ;^) I don't think that the XBitHack is required when the includes are called from within perl scripts? R.
On Wed, 2002-03-20 at 17:30, Roger Buck wrote:
Roger Buck wrote:
Suggestion:
The navigation map (crc-crc.gif and related stuff) should be included by default in each koha (intranet) page header ?
I have traced the source of this problem here.
The page headers and footers are loaded as Server Side Includes from /pathtokoha/includes/*.inc
AFAIC, for the headers and footers to be loaded from *.html files, Apache 1.2 and greater requires "XBitHack" parameter to be enabled in httpd.conf (may be different on other webservers).
Hi Roger What we normally do is just AddType text/html .shtml AddHandler server-parsed .shtml In this case its the .html pages we want to parse so we can just go AddHandler server-parsed .html (Inside the <Directory> or <Location> block) (this means we dont have to chmod any files) Hope this makes sense Chris -- Chris Cormack Programmer 025 500 789 Katipo Communications Ltd chris@katipo.co.nz www.katipo.co.nz
Hi Chris, [--snip--]
AFAIC, for the headers and footers to be loaded from *.html files, Apache 1.2 and greater requires "XBitHack" parameter to be enabled in httpd.conf (may be different on other webservers).
Chris Cormack wrote:
What we normally do is just AddType text/html .shtml AddHandler server-parsed .shtml
In this case its the .html pages we want to parse so we can just go
AddHandler server-parsed .html
(Inside the <Directory> or <Location> block)
(this means we dont have to chmod any files)
Hope this makes sense
Yep understood - and it does make sense. But... As I understand it, by default, apache does not not look for SSI commands in *.html because that slows down every access to every HTML file. On the other hand, if most koha *.html files are likely to contain includes then that alone would not be significant. OTOH, I'm unsure as to how that affects document caching... potential additional performance degradation as perceived by end user due to absence of caching? I guess the XBitHack option optimises performance (both caching and off the server) at the expense of more complex configuration requirement on the server admin. As usual, I guess it's a question of trading off ease of configuration against performance? But, for either option to work, most users will need to change their httpd.conf configuration anyhow - so maybe it's just enough to list the pros and cons and let each user make their own choice :-) BTW I noticed one other prob with the includes: Some of the tags are malformed: Instead of this: <!--#element attribute=value attribute=value --> there is this: <!--#element attribute=value attribute=value> -------------------------------------------^^ which results in a "premature EOF" I don't want you to get the wrong idea: I really don't know much about this stuff - just repeating what I've read in the docs :-) R.
On Wed, 2002-03-20 at 18:32, Roger Buck wrote:
Yep understood - and it does make sense.
But...
As I understand it, by default, apache does not not look for SSI commands in *.html because that slows down every access to every HTML file.
On the other hand, if most koha *.html files are likely to contain includes then that alone would not be significant. OTOH, I'm unsure as to how that affects document caching... potential additional performance degradation as perceived by end user due to absence of caching?
Yeah, Id recommend only turning it on for the koha dirs, since i think every .html file in there actually has an include call in it.
I guess the XBitHack option optimises performance (both caching and off the server) at the expense of more complex configuration requirement on the server admin.
As usual, I guess it's a question of trading off ease of configuration against performance? But, for either option to work, most users will need to change their httpd.conf configuration anyhow - so maybe it's just enough to list the pros and cons and let each user make their own choice :-)
Good plan.
BTW I noticed one other prob with the includes: Some of the tags are malformed:
Instead of this: <!--#element attribute=value attribute=value -->
there is this: <!--#element attribute=value attribute=value> -------------------------------------------^^
which results in a "premature EOF"
Ahh right, if you can send me a list of the files you spot this in, ill tidy that up.
I don't want you to get the wrong idea: I really don't know much about this stuff - just repeating what I've read in the docs :-)
No worries I appreciate all the work your doing, and Im sure everyone else does as well Chris -- Chris Cormack Programmer 025 500 789 Katipo Communications Ltd chris@katipo.co.nz www.katipo.co.nz
Hi Chris, I am travelling and this will be my last message here for next 24-48 hours. See attachment of tag errors grep'd from latest cvs. Toodle-oo, R.
BTW I noticed one other prob with the includes: Some of the tags are malformed:
Instead of this: <!--#element attribute=value attribute=value -->
there is this: <!--#element attribute=value attribute=value> -------------------------------------------^^
which results in a "premature EOF"
Ahh right, if you can send me a list of the files you spot this in, ill tidy that up. [--snip--]
author-demo.html:<!--#INCLUDE VIRTUAL="/includes/aquisitions-bottom.inc"> basket.html:<!--#INCLUDE VIRTUAL="/includes/aquisitions-bottom.inc"> demo-detail.html:<!--#INCLUDE VIRTUAL="/includes/aquisitions-bottom.inc"> demo.html:<!--#INCLUDE VIRTUAL="/includes/aquisitions-bottom.inc"> index.html:<!--#INCLUDE VIRTUAL="/includes/aquisitions-bottom.inc"> invoice.html:<!--#INCLUDE VIRTUAL="/includes/aquisitions-bottom.inc"> item.html:<!--#INCLUDE VIRTUAL="/includes/aquisitions-bottom.inc"> new-basket.html:<!--#INCLUDE VIRTUAL="/includes/aquisitions-bottom.inc"> new-biblio.html:<!--#INCLUDE VIRTUAL="/includes/aquisitions-bottom.inc"> order.html:<!--#INCLUDE VIRTUAL="/includes/aquisitions-bottom.inc"> periodical-order.html:<!--#INCLUDE VIRTUAL="/includes/aquisitions-bottom.inc"> periodical-receive.html:<!--#INCLUDE VIRTUAL="/includes/aquisitions-bottom.inc"> receive-multi.html:<!--#INCLUDE VIRTUAL="/includes/aquisitions-bottom.inc"> receive-order.html:<!--#INCLUDE VIRTUAL="/includes/aquisitions-bottom.inc"> receive.html:<!--#INCLUDE VIRTUAL="/includes/aquisitions-bottom.inc"> recieve-basket.html:<!--#INCLUDE VIRTUAL="/includes/aquisitions-bottom.inc"> recieve-order.html:<!--#INCLUDE VIRTUAL="/includes/aquisitions-bottom.inc"> recieve.html:<!--#INCLUDE VIRTUAL="/includes/aquisitions-bottom.inc"> supplier.html:<!--#INCLUDE VIRTUAL="/includes/aquisitions-bottom.inc"> dailyreport.html:<!--#INCLUDE VIRTUAL="/includes/reports-bottom.inc"> index.html:<!--#INCLUDE VIRTUAL="/includes/reports-bottom.inc"> index-old.html:<!--#INCLUDE VIRTUAL="/includes/members-bottom.inc"> index.html:<!--#INCLUDE VIRTUAL="/includes/members-bottom.inc"> <!--#INCLUDE VIRTUAL="/includes/issues-bottom.inc"> index-old.html:<!--#INCLUDE VIRTUAL="/hdl/intranet/includes/cat-bottom.inc">
On Wed, 2002-03-20 at 21:04, Roger Buck wrote:
Hi Chris, I am travelling and this will be my last message here for next 24-48 hours.
See attachment of tag errors grep'd from latest cvs.
Toodle-oo,
R.
Ok, This is the kick in the pants i needed to go clean up the koha-html cvs tree, lots of the files mention in that grep are mockups that we used to design the scripts, i think in fact just the index.html ones are used. So ill go through and tidy them up, removing the ones not needed Chris -- Chris Cormack Programmer 025 500 789 Katipo Communications Ltd chris@katipo.co.nz www.katipo.co.nz
Hi Chris - thanks for the cvs cleanup. I am logged in on flying visit so this will be short: I note two hard coded paths could cause problems for most users: in "groups.pl" (/pathto/overdue.jpg) in "showbudget.pl" (/pathto/budgets.inc) I also note the following regarding showbudget.pl and budgets.inc Current setup requires that apache user has write rights to the folder containing budgets.inc (under current setup this means apache user has rights to koha include folder)? Is it possible to modify showbudget.pl so that it prints out direct to the window.acquisition.index.html web page instead of to filehandle (same method that you have used in currency.pl)? If so, I think that would overcome ownership and possibly other problems related to using include? Anyhow... I hope to be able to spend some more time on this over the coming weekend. Please don't hesitate to point me in right direction if there's anything more productive. Cheers, R.
In the cvs opac-html/index.html there is a link to: /cgi-bin/koha/opac-search.pl ----------^^^^ ...shouldn't that be: /cgi-bin/opac/opac-search.pl ----------^^^^ Also, "opac-search.pl" is missing from cvs. R.
There are some inconsistencies in the content of files in koha/includes compared with same filenames in opac/includes. To prevent this (version control) problem, any reason not to merge the koha and opac includes into one single includes folder? I can't see any security issues in doing that? I think this would also allow for a single, global "includes=" path to be set in koha.conf and avoid the necessity of manually editing the path variable in each copy of Output.pm? R.
On Thu, 2002-03-21 at 23:40, Roger Buck wrote:
In the cvs opac-html/index.html there is a link to:
/cgi-bin/koha/opac-search.pl ----------^^^^
...shouldn't that be:
/cgi-bin/opac/opac-search.pl ----------^^^^
Also, "opac-search.pl" is missing from cvs.
I havent started cleaning up the opac html yet. (opac-search.pl) is no longer used. Chris -- Chris Cormack Programmer 025 500 789 Katipo Communications Ltd chris@katipo.co.nz www.katipo.co.nz
On Thu, 2002-03-21 at 23:18, Roger Buck wrote:
Hi Chris - thanks for the cvs cleanup.
I am logged in on flying visit so this will be short:
I note two hard coded paths could cause problems for most users:
in "groups.pl" (/pathto/overdue.jpg) in "showbudget.pl" (/pathto/budgets.inc)
I also note the following regarding showbudget.pl and budgets.inc
Current setup requires that apache user has write rights to the folder containing budgets.inc (under current setup this means apache user has rights to koha include folder)?
Ahh looks like showbudget.pl needs an update. It doesnt write to an inc file anymore. Ill update the cvs tree. Chris -- Chris Cormack Programmer 025 500 789 Katipo Communications Ltd chris@katipo.co.nz www.katipo.co.nz
participants (2)
-
Chris Cormack -
Roger Buck