From this IRC conversation: <fridolin> rkrimme1: did you flush memcached ? <magnuse> can't hurt :-) <magnuse> and yeah, i think you have to, for changes to koha-conf.xml to be picked up if this is the case, when creating and accessing memcached for koha-conf values, the actual modification time of the koha-conf should be appended to the key values. This means that if the file is updated, the cache is automatically invalid. It requires running stat on each request, but as the koha-conf file isn't actually being opened and parsed, this will be very fast.
Created attachment 86628 [details] [review] Bug 22473: flush in psgi - V1 Here we are checking on each request That could work, but do not feel robust Moreover it will not affect scripts outside of plack
Created attachment 86629 [details] [review] Bug 22473: Two other places that do not work - V2
Created attachment 86630 [details] [review] Bug 22473: Handle config expiration in C4::Context->new - V3
Created attachment 86631 [details] [review] Bug 22473: Example of watcher to invalidate config cache - V4 Test plan: perl watchfile.pl then update the config Note that we do not handle everything, for instance the DB credentials will not be taken into account. I guess we could call C4::Context->dbh({ new => 1 }) as well.
Here are 4 versions (to apply and test separately) that could work. Only the last one (V4) is, in my opinion, viable.
Not forgotten about this, it's just in a long queue to take a look.. Thanks for all the alternations to look at Jonathan.. I hope to come back to this soon and take a proper look :)