#802 - [Status page] - Migrate to Kuma - Disroot/Disroot-Project - Disroot Forgejo: Brace yourself, merge conflicts ahead.

muppeth commented

2024-03-02 15:41:39 +01:00

Owner

When moving from cachet we have had a choice between Kuma and cstate. At the end we have chosen cstate because it did not require javascript. However, this means the status of service needs to be manually adjusted unlike kuma that does show uptime on its own. On last deployment me snd @meaz were talking and thought to maybe move to kuma instead. It's going to make the status page more reliable as it will show whether the service is up or down in realtime, it will still allow us to send info on planned maintenance or when downtime fo the service is long.

I made a role for kuma when we were testing possibilities back then, so I need to check it out and update it.

When moving from cachet we have had a choice between Kuma and cstate. At the end we have chosen cstate because it did not require javascript. However, this means the status of service needs to be manually adjusted unlike kuma that does show uptime on its own. On last deployment me snd @meaz were talking and thought to maybe move to kuma instead. It's going to make the status page more reliable as it will show whether the service is up or down in realtime, it will still allow us to send info on planned maintenance or when downtime fo the service is long. I made a role for kuma when we were testing possibilities back then, so I need to check it out and update it.

muppeth added this to the 24.03 - March milestone 2024-03-02 15:41:39 +01:00

muppeth self-assigned this 2024-03-02 15:41:39 +01:00

muppeth added this to the (deleted) project 2024-03-02 15:41:39 +01:00

muppeth referenced this issue

2024-03-02 15:42:49 +01:00

Current state of status.disroot.org #801

floss4good commented

2024-03-06 13:09:11 +01:00

From my point of view, a downside with Kuma is that they don't provide RSS updates.

As someone mentioned on the associated feature request, they currently have a push-like notification system:

RSS feeds are more of a "pull" model (client periodically pulls information), and the current notification in uptime kuma is more of a "push" model (server sends a notification which is pushed to the client).

From my point of view, a downside with Kuma is that they don't provide RSS updates. As someone mentioned on the [associated feature request](https://github.com/louislam/uptime-kuma/issues/1673), they currently have a push-like notification system: > RSS feeds are more of a "pull" model (client periodically pulls information), and the current notification in uptime kuma is more of a "push" model (server sends a notification which is pushed to the client).