+1
Van: koha-devel-boun...@lists.koha-community.org
Namens Tomas Cohen Arazi
Verzonden: woensdag 18 april 2018 20:46
Aan: koha-devel
Onderwerp: [Koha-devel] OAuth2 - client credentials fr 18.05
Hi, during the 18.05 release cycle a lot of progress has been made towards the
goal of having a RES
+1
I think the OAuth2 client credentials grant is totally the right way to go.
While I haven’t done much with the REST API yet, I hope to make use of it a lot
in the future, so I really appreciate all the hard work everyone is doing on
this!
David Cook
Systems Librarian
Prosentient
It looks like the Koha instance on RHEL 6.9 using Perl 5.10.1 is version
3.20.x. (It may be worth noting it isn't available on the Internet; it's on a
private network.) Looks like 3.20.0 was a May 2015 release, so it is getting
long in the tooth, although not quite as long as 3.8.0, which was in
Hi, during the 18.05 release cycle a lot of progress has been made towards
the goal of having a REST api.
We voted the written and discussed RFC for the endpoints there was need to
have [1]
Some of them are already in master for 18.05, others are WIP. But the fact
we have some roadmap of things we
On 2018-04-18 09:57 AM, Jonathan Druart wrote:
We have Koha running on a RHEL 6 instance which uses 5.10.1, and it seems
to be doing fine so far. It is an older version of Koha though.
Which version is "an older version of Koha"?
Hesitating to intervene, but as a point of reference, we have
I think the first step to fight with this problem is bug 17600 -
Standardize the EXPORT
On Tue, 17 Apr 2018 at 22:05 Barton Chittenden
wrote:
> Continuing to fiddle around with this. I commented out all of the use
> statements in C4/Reserves.pm, then uncommented them one by one until the
> circu
> We have Koha running on a RHEL 6 instance which uses 5.10.1, and it seems
to be doing fine so far. It is an older version of Koha though.
Which version is "an older version of Koha"?
On Tue, 17 Apr 2018 at 22:36 David Cook wrote:
> Hi Jonathan,
>
>
>
> Thanks for reverting that patch.
>
>
>
>
Benjamin,
It's a midterm plan: we have a .gitlab-ci.yml (
https://tree.taiga.io/project/joubu-koha-rm-1711/us/146) which may need
more work (I have no idea if I have shared it on the list yet).
The problem is that we are waiting for the gitlab team to implement the
view for junit files (the ones p
I agree that official Docker images are a fantastic idea!
One of the benefits of using Docker images for most of our CI logic is that
it makes moving from one CI system to another quite easy!
I love the idea of having an official 'base' image that we can than add on
top of to create things like a
