datascijedi / website

https://datascijedi.org
Creative Commons Attribution Share Alike 4.0 International
5 stars 2 forks source link

Netlify deploys fail sometimes due to API rate limit #84

Closed ravicodelabs closed 1 year ago

ravicodelabs commented 1 year ago

The Netlify deploys and deploy previews are sometimes failing and the deploy logs state "API rate limit exceeded."

Example: https://app.netlify.com/sites/datascijedi/deploys/6421a507b7bd690008c076b4

The details of why this is happening are still unclear and may be on the GitHub side. As a temporary workaround, re-triggering the deploy (e.g. from the Netlify side or by adding additional commits) seems to work so far.

ravicodelabs commented 1 year ago

I have opened an issue with Quarto: https://github.com/quarto-dev/netlify-plugin-quarto/issues/7

ravicodelabs commented 1 year ago

A backup option for manual deploying the website via a GitHub workflow has been added. If a Netlify production deploy fails (e.g. if you don't see the change reflect on the website), you can trigger a manual deploy with the following steps:

Technically this could have small differences from the official Netlify deploy option, but it should be close enough to use for a backup option. Also, this is only set up for production deploys (not deploy previews from branches).

ravicodelabs commented 1 year ago

I have just updated the deploy method to use a temporary workaround (on the Netlify side), so hopefully deploys and deploy previews should work again now. Will keep this open for now in case a better solution comes up, e.g. if the Quarto folks have any suggestions on getting their netlify-plugin-quarto deploy plugin working for us without hitting the rate limit issue.

ravicodelabs commented 1 year ago

I have moved the Netlify deployment config and scripting to the new files netlify.toml and netlify_deploy.sh. The latter can now serve as a reference for and be used to update the Quarto version for used Netlify deploys.

Files:

ravicodelabs commented 1 year ago

The approach mentioned in my last comment (added in 65e2844) seems to be working well and also allows changing the Quarto version fairly easily, so I am closing this issue. If it still makes sense, we can potentially switch back to using netlify-plugin-quarto if https://github.com/quarto-dev/netlify-plugin-quarto/issues/7 is addressed in the future.

ravicodelabs commented 1 year ago

Some notes on deployment and Quarto version have been added here:

https://github.com/datascijedi/website/blob/main/CONTRIBUTING.md