Guilhem Bonnefille (CS) (gbonnefille)2022-10-21 13:54 Effectively, I have better success by providing a REDIS server and settings the 3 var env: TULEAP_FPM_SESSION_MODE, TULEAP_REDIS_SERVER and TULEAP_REDIS_PASSWORD. I don't know what is better: make REDIS mandatory or automatically disable all plugins that depend on such feature when it is not present, with a warning. Having a varenv in the Docker where I can set requested plugins is also a solution, probably simpler to implement and offering more possibilities.
Manuel Vacelet (vaceletm)2022-10-21 09:47 For the record, some part of Tuleap requires a redis server to work properly. The plugins now verify this constraint before being activated. The proper way to fix the OP is to add a redis server to the stack or not to activated MediaWiki Standalone. Status changed from Under review to Declined
Thomas Gerbet (tgerbet)2022-10-20 18:14 gerrit #27010 has been declined following @vaceletm comments.
Guilhem Bonnefille (CS) (gbonnefille)2022-10-20 17:58 Please, note that the ability to control the list of plugins installed (activated) in the Docker could be really useful to mitigate such problems.
Guilhem Bonnefille (CS) (gbonnefille)2022-10-20 17:56 I used the tuleap-helmchart (https://github.com/CS-SI/tuleap-helmchart) and I deployed a Redis server. And so, I found the issue: https://github.com/CS-SI/tuleap-helmchart/issues/8
Thomas Gerbet (tgerbet)2022-10-20 17:33 Hello, Thanks for the report, this plugin requires to have the async workers available (and so a Redis instance). Making this requirement mandatory was not expected for now so I made a patch rollbacking the installation of this plugin: gerrit #27010. Status changed from New to Under review