Frank Elsinga

@uncappedshady I think this is a duplicate of https://github.com/louislam/uptime-kuma/issues/1401 If you agree please close this issue, as issue-management is harder with zombies hanging around. If you disagree, what is the...

Closing as duplicate of https://github.com/louislam/uptime-kuma/issues/1401

Referencing #4236 which did include a better mock up using the custom css feature

Closing as a duplicate of #592 as the FR is covered by said issue and said issue is more popular.

@aessing your issue is possibly unrelated to the issue you are posting in. Longhorn uses iscaci NFS under the hood as I understad it. => uptime-kuma contains a database =>...

HA will not work with uptime-kuma. Please don't run multiple instances of the same docker container as this may corrupt the database. V2 includes a version to connect to external...

> Is there an ETA No, but you can watch the progress here https://github.com/louislam/uptime-kuma/milestone/24 > or preview We are not currently in beta ⇒ no public preview is available. Some...

We are also community oriented ^^ Our contribution guide [can be found here](https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md)

> Any updates on this? Nobody has contributed a monitor until now. If you or somebody else decides to take this up, please implement the core part of the monitor...

Also note that another user (@dskvr) on [a related issue](https://github.com/louislam/uptime-kuma/issues/1073#issuecomment-1330667546) has commented on the following: > Not sure how Uptime Kuma expects users to test a `websocket`, particularly in the...