Frank Elsinga

Changing the helptexts in the disable-auth popup seems sufficient to me. No need to introduce more complexity than needed.

Where/How? I think that disabling auth disables auth entirely has the logical cause that no auth is present any longer. => don't think this needs to be added on that...

What would you like to implement concretely? I think this PR-draft is quite unclear in what it wants to add a monitor for. Basically, what you want is pre-configured monitors...

Okay, let my rephrase my core concearn: > Basically, what you want is pre-configured monitors for a boatload of status pages. I am not quite convinced that this project can...

We cannot support one monitor per single service of a single company. Monitors are currently designed to be something somewhat generic (HTTPS, GRPC, DNS, ...). I don't think this monitor...

I also just did, but I cannot reproduce this working. I am missing some part. Could you share your testing mechanism? Mine is: - ```shell docker run --rm -it -p...

Yes, master and all further feature development is v2.0 only. Given that this PR adds a feature, this is the correct branch imo. See https://github.com/louislam/uptime-kuma/issues/4500 for the status of said...

| paused | unpaused | |--------|--------| |  |  | Could you provide a concrete example how to test this? Groups work mostly as expected in the experiment I...

Please see my screenshots: I can't reproduce your steps... => need a concrete example how to test this

Okay, somehow my testing mechanism was a bit flawed. I re-tried reproducing it on https://uptime.kuma.pet/ monitoring https://beeceptor.com/ was able to do so.