search

beyarkay / eskom-calendar

Get your loadshedding schedule in your calendar and never be left in the dark! Open-source, up-to-date, and developer friendly.
https://eskomcalendar.co.za
GNU General Public License v3.0
190 stars 35 forks source link

Keep track of download statistics #39

Open beyarkay opened 2 years ago

beyarkay commented 2 years ago

Currently there's no way to keep track of which calendars are being downloaded and which are not, or even how many times any calendar has been downloaded.

Having this knowledge might be important in the future for knowing which calendars are less used and therefore less critical to having higher uptime. Also having some visibility into how many people are using the calendars would be motivating for continuous improvements.

kefir500/github-release-stats or Somsubhra/github-release-stats might be able to solve this, although the download stats look to reset every time the assets are updated so there would have to be some way to cache the release stats in builld_calendars.yaml so that they don't get lost.

Ruandv commented 2 years ago

Those stats are retrieve from the same API calls I referred to in #16. If you want to keep more detailed history then you'd have to look at either adding something like google analytics (which can give you a lot of extra data) or if you don't need that then you can write a script that crawl through all your tags and do aggregate the data.

beyarkay commented 2 years ago

Hmm. Okay thanks for the dig. So what I might do is setup a GitHub action that gets the download data from the GitHub API and saves it somewhere. It seems like the download data gets reset everytime the release is updated, so the action would have to run every time a release is about to be updated