@MiaoMint @OshekharO what would be a better way to do it?
this is what I can think of as opposed to manually or using the earlier one on test branch
in this one we could make //@website required and probably in api based extension ensure they point it to a working path then set the website url through the "Miru-Url" header or another description field can be added.
in the second one where we can mimic miru and just test the latest method, but i'm not sure if it's a better way
This are just my thoughts and views what do you think?
this pr is based of issue #133
I added a file
status.go
which will perform the http request to check if the website is up and return 1 or 0 for each extensionI also added a column on the README table displaying "Ok" or "Down" based on the return status
finally the status for each extension is included in the
index.json
file that is savedeg:
current issues causing status 0
Most extensions use an api service which mostly return a 403 page when you
GET /
example agedm.orgSome extensions don't have a website url, or the url has an incorrect syntax eg. vod.api.json.collection18.js, com.freexcomic ...
@MiaoMint @OshekharO what would be a better way to do it?
this is what I can think of as opposed to manually or using the earlier one on test branch
in this one we could make //@website required and probably in api based extension ensure they point it to a working path then set the website url through the "Miru-Url" header or another description field can be added.
in the second one where we can mimic miru and just test the latest method, but i'm not sure if it's a better way
This are just my thoughts and views what do you think?