A new request with request id 17762 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is :
Title : Koha-devel Digest, Vol 187, Issue 7
Category :
Description : 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: Columns settings fails (Jonathan Druart)
2. First big moves for 21.06 - early pushes (Jonathan Druart)
3. Notes about Docker Swarm / Portainer and Koha (Tomas Cohen Arazi)
----------------------------------------------------------------------
Message: 1
Date: Fri, 11 Jun 2021 13:47:18 +0200
From: Jonathan Druart <jonathan.druart@bugs.koha-community.org>
To: Stefano Bargioni <bargioni@pusc.it>
Cc: koha-devel <koha-devel@lists.koha-community.org>
Subject: Re: [Koha-devel] Columns settings fails
Message-ID:
<CAJzKNY7ffy=3aD5t=-ReKJu-t2=_JamphZ7M45v-bO0uwW_7cA@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Hello Stefano,
This idea has been discussed on bug 16881.
It's also indirectly related to bug 27467.
Cheers,
Jonathan
Le mar. 8 juin 2021 à 14:21, Stefano Bargioni <bargioni@pusc.it> a écrit :
>
> Hi,
> imho, Columns settings in circ/circulation.pl (while checking out) doesn't save columns chosen by the librarian.
> This behaviour is expected by my staff.
> Any opinion?
> Thx. Stefano
> _______________________________________________
> 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: 2
Date: Fri, 11 Jun 2021 16:59:00 +0200
From: Jonathan Druart <jonathan.druart@bugs.koha-community.org>
To: koha-devel <koha-devel@lists.koha-community.org>
Subject: [Koha-devel] First big moves for 21.06 - early pushes
Message-ID:
<CAJzKNY4_cEoB9tTDbmBNtr+cx9nhKcnm5sZqdKQFVv+FAK=0gg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Hi devs,
I'd like to see us focus on those bugs, good candidates for early push:
Bug 17600 - Standardize the EXPORT
Bug 27526 - Remove Mod/AddItemFromMarc from additem.pl (first step,
more work needed in this area)
Bug 17427 - Replace CGI::Session with Data::Session
Bug 25078 - Update DB process - wrap each DBRev inside a transaction
and better error handling (need it soon to prevent unnecessary work
later when lot of DBrevs will exist in 21.06)
I am going to provide an updated version for the last one, the others
are ready for testing.
Hoping to see some help there :)
Cheers,
Jonathan
------------------------------
Message: 3
Date: Fri, 11 Jun 2021 12:04:54 -0300
From: Tomas Cohen Arazi <tomascohen@gmail.com>
To: koha-devel <koha-devel@lists.koha-community.org>
Subject: [Koha-devel] Notes about Docker Swarm / Portainer and Koha
Message-ID:
<CABZfb=XP=fgCrsa7J3msehz71Qur-_qwkTgtxc=JwiudgCoWFg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
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).
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
- portainer.koha-community.org
- 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)
✆ +54 9351 3513384
GPG: B2F3C15F
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20210611/5a8ba0e0/attachment-0001.htm>
------------------------------
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 7
******************************************
NOTE: You are receiving this mail because, the Requester/Technician wanted you to get notified on this request creation.