Closed tdulcet closed 1 year ago
Nice work on this!
I do prefer a more portable approach but I guess this is good enough in the mean while.
Note that I've invited you as collaborator on this repository, if you'd like, so we can merge things like this quicker.
Thank you for the invite!
Yeah, this was only meant to be a temporary solution... Personally, I liked my proposal in #32 to use Upptime, as it does the checking entirely with GitHub Actions, but that would of course be more work to setup. I did not get any responses in #32, so I was unsure of your thoughts. Anyway, I can reopen #32 to track finding a better long-term solution.
It looks like Shields.io is unwilling to find a fix for https://github.com/badges/shields/issues/9155, so this solution might also not work after all.
I used an old Uptime Robot account I had to generate the "monitor specific API keys" needed for the badges and to create the status page. I can send you an e-mail with the username and password for this account. We would need to generate a new API key if/when someone wants to add a new Send instance to this list in the future.
Edit: I just filed https://github.com/badges/shields/issues/9155 about some of the badges erroneously saying "invalid".