Greetings,
There are multiple ways to set up koha (packages, git, tarball), and there are
multiple ways to set up apache (named virtual hosts or port-based). The
packages instructions use Named Virtual Hosts. And because of the name
difference, they can be on the same port. The git instructions, if you compare,
use a port-based set up. Both are functional and correct. A named virtual hosts
set up makes more sense for packages, particularly if you wish to put it on the
internet, so people can put holds on books, and then come to the library to
pick the books up. In the case of a git set up, it is a development set up. You
are not likely to set it up on the internet, because the data is probably bogus
or filled with problems, because of testing that has been done.
There is no error. Cross-reference this to the canonical DEBIAN instructions:
http://wiki.koha-community.org/wiki/Koha_3.8_on_Debian_Squeeze#Initial_Configuration
You will see they are identical. This is correct. Do not change anything.
Now to be fair, you can put any port other than 80. But it doesn’t make sense
to go to:
https://library-intra.framisdooby.org:8080/ and
https://library.framisdooby.org/
A port change and a name change combined is just plain over-complicated. So, if
you were going to be completely port-based,
INTRAPORT="8080" # TCP listening port for the administration interface
INTRAPREFIX="" # For administration interface URL: Prefix to be added to
the instance name.
INTRASUFFIX="" # For administration interface URL: Suffix to be added to
the instance name.
would make more sense. The point of each value is to give flexibility in the
apache configuration.
Hope this explains things a bit.
GPML,
Mark Tompsett
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/