Open Jehan opened 7 years ago
P.S.: by the way, since a flatpak repo is serving static files, I'd assume that getting stats is just a matter of looking at logs. But the problem is that I am not sure what to look at.
Well I could look at .flatpakref
download but it doesn't necessarily indicate that one made the actual install, and it doesn't indicate all installs either (what if you installed the flatpakrepo instead then browsed for apps?), nor will indicate the arch. Also it doesn't indicate updates.
Apart from this, and a few /config and /summary and and/summary.sig, I see mostly a lot of /objects/some/hash/
download in my logs.
I know that if I look at refs/heads/app/org.gimp.GIMP/x86_64/master
for instance, I get the hash for the head of the GIMP app in x64-64 (master branch). Maybe I can consider the download of the corresponding /objects/this/hash.commit
as installing/updating the application? Though it would also need to download various .file
but should stats this detailed? Also still how to differentiate an install and an update then?
Well basically a lot of questions about what to look for (or a tool if you have done one already).
Basically, this is a tool that can rewrite the http log to "what app was it acutally downloading". You point it at the repo and it downloads all the commit objects (in update_mirror.sh), these are then used by e.g. histogram.sh to generate a download histogram for the app. You just feed the http logs as args to it.
This code is not really production quaility, but i'm sure you can get it running with minor tweaks.
Hi!
Considering the repo name, is it to get statistics out of a flatpak repository you manage? I'd be interested by such thing (how many install and update of which app…). But there are no README to know how to use.
Also will flathub have stats for the apps it provides?