Knot health check endpoint? #464

Thanks, good idea. I'll add one to the unauthenticated internal server if that works.

+1 I'd like this as well.

When I visit https://tangled.sh/@polarhive.net/nimbus it says:

503 — unable to reach knot We were unable to reach the knot hosting this repository. Try again later.

Here's what I did: 0. Followed the README to setup a knot on my VPS (manual)

1. Generated the secret, and verified my knot
2. Restarted VPS, systemd logs look fine
3. Made a new repository called nimbus, picked my knot
4. I visit the repo link and it threw the 503 error
5. I thought I had to push something for it to work, so I set the upstream url to: git@git.polarhive.net:polarhive.net/nimbus and pushed but nothing changes.

I don't know what broke. Is there a way to delete my knot and start the verification process again?

Welp, managed to get it to work switched to nginx.. but a health check endpoint would be really cool!

a simple check now that we have xrpc is to use /xrpc/sh.tangled.knot.version on your knot!