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: Optimizing Starman startup (Victor Grousset/tuxayo)
2. Why is config ($KOHA_CONF) stored in memcached ? (Julian Maurice)
3. Koha Community Newsletter: April 2021 (Koha Newsletter)


----------------------------------------------------------------------

Message: 1
Date: Fri, 30 Apr 2021 17:36:17 +0200
From: Victor Grousset/tuxayo <victor@tuxayo.net>
To: dcook@prosentient.com.au, 'Koha Devel'
    <koha-devel@lists.koha-community.org>
Subject: Re: [Koha-devel] Optimizing Starman startup
Message-ID: <c27befe6-eef1-0491-f200-7f4783994003@tuxayo.net>
Content-Type: text/plain; charset=utf-8; format=flowed

Great results! Thanks for pushing this :)

On 21-04-29 02:00, dcook@prosentient.com.au wrote:
> As I mentioned before, we probably won't be able to skip the validation for years, unless we roll our own Mojolicious::Plugin::OpenAPI...

Or install via CPAN for instances that are facing the issue?

Cheers,

--
Victor Grousset/tuxayo


------------------------------

Message: 2
Date: Fri, 30 Apr 2021 19:19:07 +0200
From: Julian Maurice <julian.maurice@biblibre.com>
To: koha-devel <koha-devel@lists.koha-community.org>
Subject: [Koha-devel] Why is config ($KOHA_CONF) stored in memcached ?
Message-ID: <2c158374-dc30-2bc6-09fa-1ffd91aedd47@biblibre.com>
Content-Type: text/plain; charset=utf-8; format=flowed

Hi all,

Maybe it's a dumb question, but I don't understand why the config is
stored in memcached as:
- memcached server address is in this config, so we need to read
$KOHA_CONF file first in order to connect to memcached server
- config is kept in memory forever ($C4::Context::context), so we
shouldn't need the cache once starman has started.

If you add a warning in Koha::Config::read_from_file, you'll see that
the file is read 3 times per worker, even when the config already exist
in cache (it's read 4 times when the cache is empty).
It's read each time we call Koha::Cache->new (+ in C4::Context->new if
the cache is empty)

Shouldn't we read the file only in C4::Context->new (without using
cache), and make Koha::Cache use C4::Context->config instead ?

--
Julian Maurice
BibLibre


------------------------------

Message: 3
Date: Sat, 1 May 2021 00:25:44 +0200
From: Koha Newsletter <kohanews@gmail.com>
To: koha <koha@lists.katipo.co.nz>, koha-devel
    <koha-devel@lists.koha-community.org>
Subject: [Koha-devel] Koha Community Newsletter: April 2021
Message-ID:
    <CAEqgz_kM3A=shLmWV9qbwpEbqQDpZK+F6Y3mbPNX4mygzFXZ2w@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

The Koha Community Newsletter for April 2021 is here:
* https://koha-community.org/koha-community-newsletter-april-2021/

Many thanks to everyone who submitted articles and news to last month's
newsletter!

Please feel free to email me with any corrections or suggestions.
--
Michael Kuhn
Editor, Koha Community Newsletter
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20210501/ac279fc4/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 186, Issue 1
******************************************