Re: [Koha] Koha Digest, Vol 115, Issue 44
It is tested on server and running well. The port 8000 is automatically added at the bottom of file and it does not affect the installation. The script is written considering those people who finds difficulty in installation specially dealing with Linux OS. Working with Linux OS is a still big challenge for people working in small libraries. Since, they don't have any good ILMS so they opt Koha for housekeeping operation. I personally have conducted many training and workshop and found that installation of Koha itself is a big challenge for them. The information given on sites is not self explanatory for installation. Thanks for your advice and comments. On Thu, May 28, 2015 at 5:30 AM, <koha-request@lists.katipo.co.nz> wrote:
Send Koha mailing list submissions to koha@lists.katipo.co.nz
To subscribe or unsubscribe via the World Wide Web, visit https://lists.katipo.co.nz/mailman/listinfo/koha or, via email, send a message with subject or body 'help' to koha-request@lists.katipo.co.nz
You can reach the person managing the list at koha-owner@lists.katipo.co.nz
When replying, please edit your Subject line so it is more specific than "Re: Contents of Koha digest..."
Today's Topics:
1. Re: [Koha-devel] Install Koha 3.20 with Single Command at Ubuntu 14.04 LTS (Robin Sheat)
----------------------------------------------------------------------
Message: 1 Date: Thu, 28 May 2015 11:46:54 +1200 From: Robin Sheat <robin@catalyst.net.nz> To: koha-devel@lists.koha-community.org, koha <koha@lists.katipo.co.nz> Subject: Re: [Koha] [Koha-devel] Install Koha 3.20 with Single Command at Ubuntu 14.04 LTS Message-ID: <1432770414.25145.113.camel@catalyst.net.nz> Content-Type: text/plain; charset="utf-8"
DP Tripathi schreef op wo 27-05-2015 om 11:53 [+0530]:
Just follow the instructions.
Some pretty minor issues to start with:
Why does it do this:
sed -e 's/ident//; s/sameuser/trust/' /etc/apache2/ports.conf.dpt > /etc/apache2/ports.conf then: sed -e 's/ident//; s/sameuser/trust/' /etc/mysql/my.cnf.dpt > /etc/mysql/my.cnf then: sed -e 's/ident//; s/sameuser/trust/' /etc/perl/XML/SAX/ParserDetails.ini.dpt > /etc/perl/XML/SAX/ParserDetails.ini ?
also, rewriting the ParserDetails.ini hasn't been needed for a long time.
The code does stuff on port 8000, but the messages talk about port 8080. I think in general 8080 is the more common port to set up secondary webservices on.
The last echo writes and then immediately opens an editor to the file, so you wouldn't know what you need to do with it. If it did show the message, it would ask them to change the port, and then open firefox, assuming that it hadn't been changed. Also, if they did change it, it now wouldn't match the "Listen" line added near the top.
This looks like a reasonable quick-start to get a Koha server up, though. It won't give you nice things like name-based addressing that you'd probably want in a production server, but they'd be easy enough to add on after the fact.
-- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF
DP Tripathi schreef op do 28-05-2015 om 07:16 [+0530]:
It is tested on server and running well.
The port 8000 is automatically added at the bottom of file and it does not affect the installation.
It might work, but it does something things that aren't really correct or necessary that might prove confusing, or potentially break things under certain circumstances. For example, why are you doing what (from memory) looks like a change to make a postgresql database less secure to an apache config file, a mysql config file, and an XML parser details file? It's not something I'd expect a carefully tested script to do, and it raises doubts about the other parts of the script, like how it writes things out in a way that can't be seen and gives incorrect advice to the user. Not to mention, Koha doesn't even use postgresql. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF
participants (2)
-
DP Tripathi -
Robin Sheat