Assigning TCP ports to per-instance Koha services (e.g. koha-sip)
Hi all, I've noticed that "koha-sip" will copy /etc/koha/SIPconfig.xml into /etc/koha/sites/${name}/SIPconfig.xml, but it retains the default port of 6001. Obviously, only 1 service can bind to port 6001 inside the same network namespace, so that's only going to work once, and any following "koha-sip --enable" will need manual intervention after. Is this a convention that we should expect for all current and future per-instance Koha services using TCP ports? Or should we be thinking about ways of dynamically allocating free ports? I suppose that most multi-Koha installations will have a vendor/service provider who can easily configure backend systems, whereas many organisations without technical expertise are more likely to run only 1 Koha instance (and thus benefit from single hard-coded defaults). So maybe just hard-coding a default into a per-instance Koha service makes sense? Or having an option on CLI scripts like koha-sip to define a port (to ease things for vendors) while leaving the default for users with less complex requirements? Just curious what people think. David Cook Software Engineer Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595
Den 12.08.2020 02:49, skrev dcook@prosentient.com.au:
So maybe just hard-coding a default into a per-instance Koha service makes sense? Or having an option on CLI scripts like koha-sip to define a port (to ease things for vendors) while leaving the default for users with less complex requirements?
A --port command line option to koha-sip, with a sane default if not activated, sounds like an excellenet idea to me! Best regards, Magnus Libriotech AS
Thanks, Magnus. I've opened up the following report for it: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26198 David Cook Software Engineer Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 -----Original Message----- From: Koha-devel <koha-devel-bounces@lists.koha-community.org> On Behalf Of Magnus Enger Sent: Wednesday, 12 August 2020 5:23 PM To: koha-devel@lists.koha-community.org Subject: Re: [Koha-devel] Assigning TCP ports to per-instance Koha services (e.g. koha-sip) Den 12.08.2020 02:49, skrev dcook@prosentient.com.au:
So maybe just hard-coding a default into a per-instance Koha service makes sense? Or having an option on CLI scripts like koha-sip to define a port (to ease things for vendors) while leaving the default for users with less complex requirements?
A --port command line option to koha-sip, with a sane default if not activated, sounds like an excellenet idea to me! Best regards, Magnus Libriotech AS _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org https://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/
We should definitely make everything configurable through option switched as much as possible. El mié., 12 de agosto de 2020 22:59, <dcook@prosentient.com.au> escribió:
Thanks, Magnus.
I've opened up the following report for it: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26198
David Cook Software Engineer Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia
Office: 02 9212 0899 Online: 02 8005 0595
-----Original Message----- From: Koha-devel <koha-devel-bounces@lists.koha-community.org> On Behalf Of Magnus Enger Sent: Wednesday, 12 August 2020 5:23 PM To: koha-devel@lists.koha-community.org Subject: Re: [Koha-devel] Assigning TCP ports to per-instance Koha services (e.g. koha-sip)
Den 12.08.2020 02:49, skrev dcook@prosentient.com.au:
So maybe just hard-coding a default into a per-instance Koha service makes sense? Or having an option on CLI scripts like koha-sip to define a port (to ease things for vendors) while leaving the default for users with less complex requirements?
A --port command line option to koha-sip, with a sane default if not activated, sounds like an excellenet idea to me!
Best regards, Magnus Libriotech AS _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org https://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/
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org https://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/
participants (3)
-
dcook＠prosentient.com.au -
Magnus Enger -
Tomas Cohen Arazi