4 ms·
For some reason the Quality check was always failing with an error 403, even though I had followed the link to create a Google API key and passed it as an env v
by j1elo 2y ago
For some reason the Quality check was always failing with an error 403, even though I had followed the link to create a Google API key and passed it as an env var to the Docker container.
Ended up cloning the project to see by myself what URL it uses... turns out that the Google API was returning a JSON document with instructions to enable the PageSpeed Insights API! I'd never used Google Cloud before, so I had been a bit clueless until that point :-)
My suggestion is that the "Show Error" button showed the actual output of the API calls, because otherwise this very useful JSON from Google was being lost in translation.
Now that I checked the code it's clear that there are actually 2 things to enable that are accessed with the API key:
* PageSpeed Insights API: https://console.cloud.google.com/apis/library/pagespeedonline.googleapis.com https://console.cloud.google.com/apis/library/pagespeedonlin...
* Safe Browsing API: https://console.cloud.google.com/apis/api/safebrowsing.googleapis.com/metrics https://console.cloud.google.com/apis/api/safebrowsing.googl...
So I'd suggest adding this info to either or both of the README and the app itself.
Otherwise, a very very cool project! I've been checking several of my sites for the last hour.