Well of course, there can still be bugs in the code even if 200 is returned.
I always implement a /~/healthcheck route which will return the exit code of each check, but also encodes it in the HTTP STATUS.
if any error is detected the status will be 500
if any warning is detected it will be 200+<numberOfWarnings>
of course checks still need to be written, e.g. a code needs to verify that it can connect to ssh and is greeded with the correct login msg.
still there could be problems for outcomming connections.
I always implement a /~/healthcheck route which will return the exit code of each check, but also encodes it in the HTTP STATUS. if any error is detected the status will be 500 if any warning is detected it will be 200+<numberOfWarnings> of course checks still need to be written, e.g. a code needs to verify that it can connect to ssh and is greeded with the correct login msg.
still there could be problems for outcomming connections.