You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* feat: add CACHE_SECONDS environment variable
This commit adds the CACHE_SECONDS environment variable. This variable
can be used to circumvent our cache clamping values for self hosted
Vercel instances.
* refactor: apply formatter
-[Keep your fork up to date](#keep-your-fork-up-to-date)
116
+
-[:sparkling\_heart: Support the project](#sparkling_heart-support-the-project)
117
+
118
+
# Important Notice <!-- omit in toc -->
119
+
120
+
> **Warning**
121
+
> Since the GitHub API only [allows 5k requests per hour per user account](https://docs.github.com/en/graphql/overview/resource-limitations), the public Vercel instance hosted on `https://github-readme-stats.vercel.app/api` could possibly hit the rate limiter (see #1471). We use caching to prevent this from happening (see https://github.com/anuraghazra/github-readme-stats#common-options). You can turn off these rate limit protections by deploying [your own Vercel instance](#disable-rate-limit-protections).
102
122
103
123
# GitHub Stats Card
104
124
@@ -623,6 +643,14 @@ Since the GitHub API only allows 5k requests per hour, my `https://github-readme
623
643
5. You're done 🎉
624
644
</details>
625
645
646
+
### Disable rate limit protections
647
+
648
+
Github Readme Stats contains several Vercel environment variables that can be used to remove the rate limit protections:
649
+
650
+
-`CACHE_SECONDS`: This environment variable takes precedence over our cache minimum and maximum values and can circumvent these values for self Hosted Vercel instances.
651
+
652
+
See [the Vercel documentation](https://vercel.com/docs/concepts/projects/environment-variables) on adding these environment variables to your Vercel instance.
653
+
626
654
### Keep your fork up to date
627
655
628
656
You can keep your fork, and thus your private Vercel instance up to date with the upstream using GitHub's [Sync Fork button](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork). You can also use the [pull](https://github.com/wei/pull) package created by [@wei](https://github.com/wei) to automate this process.
0 commit comments