Send Koha-devel mailing list submissions to
koha-devel@lists.koha-community.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
or, via email, send a message with subject or body 'help' to
koha-devel-request@lists.koha-community.org
You can reach the person managing the list at
koha-devel-owner@lists.koha-community.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Koha-devel digest..."
Today's Topics:
1. Re: Notes about Docker Swarm / Portainer and Koha
(dcook@prosentient.com.au)
2. Sharing installation method with Hea (dcook@prosentient.com.au)
3. Re: Sharing installation method with Hea (Victor Grousset/tuxayo)
4. Re: Sharing installation method with Hea
(dcook@prosentient.com.au)
5. Perl syntax for strings (Fridolin SOMERS)
6. some thoughts on #28519 regarding lib (Thomas Klausner)
----------------------------------------------------------------------
Message: 1
Date: Tue, 15 Jun 2021 09:42:52 +1000
From: <dcook@prosentient.com.au>
To: "'Tomas Cohen Arazi'" <tomascohen@gmail.com>, "'koha-devel'"
<koha-devel@lists.koha-community.org>
Subject: Re: [Koha-devel] Notes about Docker Swarm / Portainer and
Koha
Message-ID: <00fd01d76176$fdd774f0$f9865ed0$@prosentient.com.au>
Content-Type: text/plain; charset="utf-8"
Sounds like a plan to me.
David Cook
Software Engineer
Prosentient Systems
Suite 7.03
6a Glen St
Milsons Point NSW 2061
Australia
Office: 02 9212 0899
Online: 02 8005 0595
From: Koha-devel <koha-devel-bounces@lists.koha-community.org> On Behalf Of Tomas Cohen Arazi
Sent: Saturday, 12 June 2021 1:05 AM
To: koha-devel <koha-devel@lists.koha-community.org>
Subject: [Koha-devel] Notes about Docker Swarm / Portainer and Koha
Hi all, for the 21.05 release, I proposed to launch the API docs site [1]. I did it on Theke's infrastructure for simplicity, but then started thinking how management could be handed to the community.
This site is provided by a docker image [2] that is built on each change on the Koha community repository. This is triggered by webhooks.
With the idea that this image should be deployed in production automatically, I deployed a Portainer service. Portainer would let us configure and deploy (dockerized) services in a fairly easy way, has an API, and also provides webhooks for triggering things like redeploying/updating (what I needed for api.koha-community.org <http://api.koha-community.org> ).
Right now this is running under Theke's umbrella, but my idea is to hand this to the community, especially those running the services we use. The short term plan would be to:
1. Have the following domains point to the server we are providing:
- traefik.koha-community.org <http://traefik.koha-community.org>
- portainer.koha-community.org <http://portainer.koha-community.org>
- api.koha-community.org <http://api.koha-community.org>
2. Migrate Jenkins into this server/setup
3. Anyone running server for community purposes, can make them join this 'swarm' so we can use them.
4. There will be some community members with admin access to this, so we can all do maintenance tasks like restarting a service, etc.
5. Help is needed regarding backups and how we want to deal with that.
We volunteer to help anyone running community sites migrate to this schema.
[1] https://api.koha-community.org
[2] https://gitlab.com/koha-community/koha-api-docs/-/pipelines/316321820
--
Tomás Cohen Arazi
Theke Solutions (http://theke.io <http://theke.io/> )
✆ +54 9351 3513384
GPG: B2F3C15F
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20210615/63a997ea/attachment-0001.htm>
------------------------------
Message: 2
Date: Tue, 15 Jun 2021 09:47:22 +1000
From: <dcook@prosentient.com.au>
To: "'koha-devel'" <koha-devel@lists.koha-community.org>
Subject: [Koha-devel] Sharing installation method with Hea
Message-ID: <010701d76177$9eeaa7e0$dcbff7a0$@prosentient.com.au>
Content-Type: text/plain; charset="utf-8"
Hi all,
I was looking at https://hea.koha-community.org/systempreferences to view
the different versions of Koha out there, and it got me thinking how it
would be nice to know how people install Koha.
I imagine that we all think that the majority of people use the Debian
packages, but it would be good to know.
What do people think?
David Cook
Software Engineer
Prosentient Systems
Suite 7.03
6a Glen St
Milsons Point NSW 2061
Australia
Office: 02 9212 0899
Online: 02 8005 0595
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20210615/725c8c6c/attachment-0001.htm>
------------------------------
Message: 3
Date: Tue, 15 Jun 2021 07:09:21 +0200
From: Victor Grousset/tuxayo <victor@tuxayo.net>
To: koha-devel@lists.koha-community.org
Subject: Re: [Koha-devel] Sharing installation method with Hea
Message-ID: <aff3b159-22ad-9237-dd97-ddf4bd31d8e5@tuxayo.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Hi :)
On 21-06-15 01:47, dcook@prosentient.com.au wrote:
> I was looking at https://hea.koha-community.org/systempreferences
> <https://hea.koha-community.org/systempreferences> to view the different
> versions of Koha out there, and it got me thinking how it would be nice
> to know how people install Koha.
>
> I imagine that we all think that the majority of people use the Debian
> packages, but it would be good to know.
>
> What do people think?
Does Koha already have data that would allow to deduce the install method?
If not, how to infer that for Debian packages?
For a git install, checking for a .git is enough.
Cheers,
--
Victor Grousset/tuxayo
------------------------------
Message: 4
Date: Tue, 15 Jun 2021 16:04:42 +1000
From: <dcook@prosentient.com.au>
To: "'Victor Grousset/tuxayo'" <victor@tuxayo.net>,
<koha-devel@lists.koha-community.org>
Subject: Re: [Koha-devel] Sharing installation method with Hea
Message-ID: <015001d761ac$55a6c160$00f44420$@prosentient.com.au>
Content-Type: text/plain; charset="utf-8"
I was wondering if Koha already had that data, but I'm not so sure.
I am thinking that "make install" would perhaps create a file containing the index method, and the Debian package build could overwrite that.
David Cook
Software Engineer
Prosentient Systems
Suite 7.03
6a Glen St
Milsons Point NSW 2061
Australia
Office: 02 9212 0899
Online: 02 8005 0595
-----Original Message-----
From: Koha-devel <koha-devel-bounces@lists.koha-community.org> On Behalf Of Victor Grousset/tuxayo
Sent: Tuesday, 15 June 2021 3:09 PM
To: koha-devel@lists.koha-community.org
Subject: Re: [Koha-devel] Sharing installation method with Hea
Hi :)
On 21-06-15 01:47, dcook@prosentient.com.au wrote:
> I was looking at https://hea.koha-community.org/systempreferences
> <https://hea.koha-community.org/systempreferences> to view the
> different versions of Koha out there, and it got me thinking how it
> would be nice to know how people install Koha.
>
> I imagine that we all think that the majority of people use the Debian
> packages, but it would be good to know.
>
> What do people think?
Does Koha already have data that would allow to deduce the install method?
If not, how to infer that for Debian packages?
For a git install, checking for a .git is enough.
Cheers,
--
Victor Grousset/tuxayo
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/ git : https://git.koha-community.org/ bugs : https://bugs.koha-community.org/
------------------------------
Message: 5
Date: Tue, 15 Jun 2021 10:19:12 +0200
From: Fridolin SOMERS <fridolin.somers@biblibre.com>
To: koha-devel <koha-devel@lists.koha-community.org>
Subject: [Koha-devel] Perl syntax for strings
Message-ID: <a8a9e336-e84d-f067-8b86-abedd038064d@biblibre.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi,
I see in Perl code some cases where a string in written with a space
between q or qq or qw and string.
Like : qq /foo bar/ instead of qq/foo bar/
It works, but I dont find it in docs like
https://perldoc.perl.org/perlop#Quote-Like-Operators
Most of cases are in :
use CGI qw ( -utf8 );
There are only 29 other cases :
git grep -E ' q[qw]? [/({]' | grep -v 'use CGI qw '
Should we add a coding guideline ?
https://wiki.koha-community.org/wiki/Coding_Guidelines
I must admint for me it would be better to avoid it because it breaks
syntax coloring in my editor (Eclipse with EPIC).
But maybe other have the same issue.
Best regards,
--
Fridolin SOMERS <fridolin.somers@biblibre.com>
Software and system maintainer 🦄
BibLibre, France
------------------------------
Message: 6
Date: Tue, 15 Jun 2021 10:48:19 +0200
From: Thomas Klausner <domm@plix.at>
To: koha-devel@lists.koha-community.org
Subject: [Koha-devel] some thoughts on #28519 regarding lib
Message-ID: <YMhpU2qjCFB2cORh@plix.at>
Content-Type: text/plain; charset=us-ascii
Hi!
without knowing a lot of Koha-internals (still..), I'd strongly prefer
to have all the code in a lib dir (as is standard in Perl apps / modules
for ages).
There are also a lot of tools available to make using code stored `lib`
(but not "installed" in the system, i.e. only available in the checkout)
easy. The simplest is of course 'lib': https://perldoc.perl.org/lib
Or more complex like https://metacpan.org/pod/lib::projectroot (which I
wrote some time ago to handle a Monorepo setup; it also includes a
comparison of different modules in the SEE ALSO section)
OTOH, CGI::Session::Serialize is a cpan module, so technically it should
not be checked out into the app code `lib`, but installed as a
dependency. There are even more ways to handle installing of
dependencies and the finding them, but the currently most comfortable
one is https://metacpan.org/pod/Carton. Or (if running everything via
Carton is too much of a change), a combination of
https://metacpan.org/pod/local::lib and a modern CPAN client
(https://metacpan.org/pod/App::cpanminus or
https://metacpan.org/pod/App::cpm.
I did not want to spam the actuall ticket with this, as I'm not sure if
any of this is in fact relevant to the bug, and/or matches the current
plans for Koha.
Greetings,
domm
--
#!/usr/bin/perl https://domm.plix.at
for(ref bless{},just'another'perl'hacker){s-:+-$"-g&&print$_.$/}
------------------------------
Subject: Digest Footer
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/
------------------------------
End of Koha-devel Digest, Vol 187, Issue 10
*******************************************