Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds two different implementations of a way to verify members of the webring.
The first,
verify.mjs
simply makes sure that the listed URL only returns a response in the2xx
range. This is a quick spot check to make sure that the site owner doesn't redirect to a different location. The second,verifyDNS.mjs
is slightly more complicated. It verifies, using DNS TXT records, whether a site owner controls their own domain by requiring a TXT record on the listed hostname. Both of these functions use Netlify's scheduled functions feature.verify
runs daily andverifyDNS
runs weekly. Obviously that timing can be changed by updating the value innetlify.toml
.Neither of these implementations solves the question as to what to do if one of these functions actually encounters that scenario. I don't know much about Netlify or whether it has logging or alerting functionality. Hopefully this helps in the discussion in #33.