Self-hosting GitHub Stats Cards to Avoid Rate Limits and Downtime

Описание и применение

Публичные сервисы статистики GitHub часто ломаются из-за общих ресурсов и лимитов API. Решение — self-hosting сервиса gitglance, который предоставляет выделенный доступ к API (5000 запросов/час) и гарантирует стабильность карточек статистики в профиле.

Задача

Public GitHub stats card services frequently break due to shared infrastructure, leading to rate limit exhaustion and deployment pauses that result in broken images on user profiles.

Результат

By self-hosting gitglance, users gain control over their GitHub API rate limits (increasing from 60 to 5,000 requests/hour) and eliminate dependency on shared public infrastructure, ensuring their profile stats cards remain functional and visually consistent.

Рабочий процесс

• Identify the instability of public stats card services due to shared resources and rate limits.
• Select a self-hostable alternative like gitglance.
• Import the gitglance repository to a hosting platform like Vercel.
• Configure the GITHUB_TOKEN environment variable with a token having public_repo scope.
• Deploy the instance to generate a unique URL for the stats card.
• Update the GitHub profile README with the new self-hosted card URL.
• Utilize the visual card builder to customize styles, themes, and card types.

Доказательства

Those services run as one shared public instance... When traffic spikes, the deployment gets paused and everyone's README breaks at once.

Источник

With your own deployed instance plus a GITHUB_TOKEN environment variable... you get 5,000 requests per hour all to yourself.

Источник