-
Notifications
You must be signed in to change notification settings - Fork 394
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve CloudFlare cache cleaner logging + Stars bugfix (second attempt) #1600
Conversation
Since Heroku's runtime logs are much trickier to track down than dyno runtime logs, this change will allow us to better see CloudFlare cache clearing feedback. The script in `clear-cloudflare-cache` is changed from a shell-invoked style to a Node module that's imported into `deploy-with-s3`.
This replaces the Node with a Resolver, so the in-between layer is thinner and not subject to stale cache pruning as it is only a middleman. This also adds `createResolvers` to Gatsby APIs exposed to Models
…x-cloudflare-cache-clearer
Yep, adding |
Deploying? :) |
Yep, it's deploying successfully now! With the slight change to the |
Yay! The site's not broken! In this aspect, at least. |
This is the same PR as before, but with a slight change to fix the server invocation.
This time I'll confirm the review app before I suggest a merge.