Running into GitHub API rate limit issues.

[MSERobert]

We have around 50 sites and lately I've been hitting the wall (hourly) on our GitHub personal access token and have a couple of questions.

How often does the git-updater run on it's own (12 hours)?

Last change I made was to enable the "Cron Optimizer" in Cloudways (which disables the wp-cron and runs the cron on a regular schedule). Could this be the cause?

Lastly, is the git-updater compatible with object cache?

Any insight would be great.

Thanks,
Robert

[afragen]

@MSERobert if you have a license properly entered for Git Updater and a Personal Access Token set for GitHub.com in the Settings, you should have 5000 API requests/hr. Without a Personal Access Token you will only have 60 API requests/hr.

Git Updater's repository caches are set to expire after 12 hours. A WP-Cron even should run every 12 hrs to update expired caches. The precise timing of this is how often your site is accessed or how often your server is set to run all pending cron jobs. My own servers have wp-cron disabled and run all pending wp-cron tasks between every 1-5 min.

Git Updater reads/write its cache to the wp_options table. To the extent that those options are retrieved via a persistent object cache, yes they are compatible. Git Updater does not directly use transients or wp_cache_*. I do run a persistent object cache, Redis, on my servers and locally for testing.

How many packages (plugins or themes) are integrated with Git Updater on any given site? There are about 6-9 API calls per package. I have well over 30 integrated packages on a single test server and the only time I ever come close is by using the Refresh Cache button over short durations for testing.

[MSERobert]

Yes, I have the Git Updater license added and a personal access token from GitHub.

I didn't realize it but it looks like we're averaging about 30 integrated plugins and a couple of themes per site times around 50 sites.

[afragen]

If all the sites share an IP address that could definitely be the issue.

[MSERobert]

It's about 10 sites per IP address. And I can't just generate another token can I, it's tied to the user?

[afragen]

I think GitHub ties the rate limit to the IP. You can generate multiple personal access tokens. I don't think that will make a difference but it's worth a try.

There might be another way. More coming.

[afragen]

Take a look at Git Updater Lite. It might avoid the rate limiting.

https://thefragens.com/git-updater-lite/

https://thefragens.com/update-api-server/

[afragen]

By using GUL and having one site as the Update API Server, one one site would send API requests to GitHub and all plugins would send API requests to the Update API Server.

Yes, it would mean adding Git Updater Lite via composer to each package. You wouldn't need to install the packages on the Update API Server, you could simply add them to the Additions tab.

[MSERobert]

Sounds interesting, I'll check it out. Thank you.