Uptime monitor

[Tealk]

Checks IP's and URL's if they are reachable and writes an entry into the database if the status changes.

Execution:
Calling the file /admin/cron.php

This shows the current status when you execute it in the browser.

Reference #3

[Pryx]

Once I merge https://github.com/server-status-project/server-status/tree/cleanup would you be interested in reworking this to match the updated version? I expect that there are changes in this PR that are not directly related to uptime monitoring, right?

BTW what does this check exactly? From the code it seems to use curl, so it checks the HTTP code returned from the server? I am wondering whether using an external service such as freshping.io and listening for updates wouldn't be better as they can probably check the services more reliably (via PING / HTTP requests and more) and it wouldn't require users to be able to set up cron.

[jhuesser]

I think an external service is better, so a user can use their preferred monitoring solution. Most of them have a webhook integration, so we could change our API to allow management of status entries.

[Tealk]

One does not exclude the other @jhuesser

[Tealk]

I expect that there are changes in this PR that are not directly related to uptime monitoring, right?

Actually, this PR should not contain anything except monitoring, but I have continued to work on codeberg for quite some time
actually it needs only the admin/cron.php and the adjustment database/admincenter so that the domain/ip can be entered there

External services are always very questionable from a data protection point of view, which is why I decided to work on the project.
if the user can't even set up a cron on a webspace, he should consider if publishing a website is the right thing to do.
All webhosts I know have a graphical interface for setting up a cron.

[Tealk]

deferred until pr #162 is done