Could you confirm that you talking about https://phetools.toolforge.org/transclusions.html ?

Indeed, it's strange that only 21 Wikisource domains are shown because the other domains stats exist but are not displayed. For instance there is https://phetools.toolforge.org/graphs/Wikisource_-_texts_eo.svg for Esperanto Wikisource. I guess it should be quite easy to fix.

PS: did you see T319965 (where it says - more or less explicitly - that the current migration might shut down this tool :/)

In T353109#9395015, @VIGNERON wrote:

Could you confirm that you talking about https://phetools.toolforge.org/transclusions.html ?

Indeed, it's strange that only 21 Wikisource domains are shown because the other domains stats exist but are not displayed. For instance there is https://phetools.toolforge.org/graphs/Wikisource_-_texts_eo.svg for Esperanto Wikisource. I guess it should be quite easy to fix.

PS: did you see T319965 (where it says - more or less explicitly - that the current migration might shut down this tool :/)

Is the current code for the tool publicly available ? It should not be hard to rewrite/decouple the statistics aspect of the tool and get it working in Kubernetes. The OCR aspect might require a lot more work.

In T353109#9395042, @Soda wrote:

Is the current code for the tool publicly available ?

Yes and no. See T319965.

In T353109#9395015, @VIGNERON wrote:

Could you confirm that you talking about https://phetools.toolforge.org/transclusions.html ?

Indeed, it's strange that only 21 Wikisource domains are shown because the other domains stats exist but are not displayed. For instance there is https://phetools.toolforge.org/graphs/Wikisource_-_texts_eo.svg for Esperanto Wikisource. I guess it should be quite easy to fix.

eo and uk graphs were already being generated, they just hadn't been added to the (static) transclusions.html so they were never displayed anywhere. I've now added them there, and it is indeed as simple as adding an extra two lines to the HTML with the relevant language codes.

For languages for which graphs are not already being generated it's a different story. These require quite a lot more work, and are highly unlikely to be added until well after the k8s migration is completed and the stats code has been modernised (it just has too much technical debt to keep patching bit by bit).