This is a new, improved version of https://github.com/awesome-selfhosted/awesome-selfhosted/
Please check the release announcement for more details.
Maintainer here, happy to answer questions.
This is a new, improved version of https://github.com/awesome-selfhosted/awesome-selfhosted/
Please check the release announcement for more details.
Maintainer here, happy to answer questions.
Very sorry for the missing attribution. I added it in the header, should be online now.
Just want to say that Im a big fan of what you guys do! Awesome Selfhosted is really great.
Regarding the topics Im also not 100% happy with it but at least it provides the ability to find projects that likely support docker for example. It would probably be great to have this kind of information inside awesome selfhosted.
More than happy to add an issue for Icons. The problem here is that repos dont actually have icons, there are only icons from the owner of the repo. So with some projects its a photo of the owner for example.
I looked a bit into how best to determine the activity level of a project and for me commit history is one of the strongest signs. Also Github uses this kind if graph in a users repo overview so its already familiar to GitHub users. There should be a label with the max number of commits to provide some scale, could be a browser problem.
There is also https://isitmaintained.com/ which measures issue resolution and percentage of open issues. But this can also be quite missleading since it shows positive for an empty repo.
Thanks for the link to the generator, I will look into it.
No problem, thanks for fixing it so quickly!
This information is already present but we need to make it easier to browse projects by platform -> https://github.com/awesome-selfhosted/awesome-selfhosted-data/issues/71
^now I see it but it’s a bit small :)^
I see, I agree it’s a good metric. I am wary of adding too much information that relies on Github APIs because 1. it encourages centralization on a proprietary platform 2. we are already running into API rate limits with just the info we currently gather (stars count + last commit date). And we would need a way to store this graph information in the raw YAML data somehow. If you want to create an issue for this, to gather more feedback and so it can be discussed further, please do!
Couldnt agree more! This is why I decided not to use discussions or issue count since those are GitHub specific. Commit count could be gathered from any platform that uses git.
Im using the GitHub GraphQL API to query all necessary information for 100 repos at a time, including commit count per month. The rate limit for GraphQL is allowing up to 5000 points per hour and on of these queries only costs 1 point. Herre is my code to generate the query: https://github.com/mkitzmann/awwesome/blob/main/src/lib/query.ts
The Informationen is currently just „{month: count,…}“, so should be fairly simple to store in yml. I will create an issue for it.
When using the automatic
GITHUB_TOKENcreated for each GH actions workflow, the limit is only 1000 requests per hour [1]. The list has 1080 projects whose source is hosted on github, and we must do 2 API calls for each one because for some reason the date of last commit to the default branch is not available directly from the repos API endpoint [2] (do not trustupdated_at/pushed_at, it’s a lie). So we currently have to add a sleep of ~7 seconds between each API call to not hit the rate limit for the metadata update job that runs daily.The limit of 5000 requests/hour only applies to personal access tokens which have far too many permissions on my personal account to be used in a shared/community project.
Someone in https://old.reddit.com/r/selfhosted/comments/15y7y36 mentioned https://analyzemyrepo.com/analyze/inventree/InvenTree which may be interesting to integrate somehow.