Current state of status.disroot.org #801

New Issue

Open

opened 2024-03-02 14:27:44 +01:00 by floss4good · 2 comments

floss4good commented

2024-03-02 14:27:44 +01:00

I think there is something wrong with the current state of Disroot State page.

On Tuesday, February 13, you added 'Maintenance window 59' and now I can't find this item within the Incident history list, although it is accessible through the assigned issue URL. Moreover, according to the git repository it is still pinned.

During the same Tuesday, few hours later (according to Thunderbird, my RSS client), the title of the 🔥️ Issue - Git (forgejo) instance is down! 🔥️ incident was updated to '[Resolved] 🔥 Issue - Git (forgejo) instance is down! 🔥' (more precisely a new RSS item was created). But on status.disroot.org the title is still the old one and the issue is now pinned; while the corresponding git file was last updated in December.

Is it possible that you have some local changes that were not pushed?
While describing this issue I also realized that it can be my fault, since I pushed a wording fix for maintenance window 59 and it might have caused a merge conflict on your side.

I think there is something wrong with the current state of [Disroot State page](https://status.disroot.org). On Tuesday, February 13, you added 'Maintenance window 59' and now I can't find this item within the Incident history list, although it is accessible through [the assigned issue URL](https://status.disroot.org/issues/2024.02.13-maintenance-window-59/). Moreover, [according to the git repository](https://git.disroot.org/Disroot/cstate-content/raw/branch/main/issues/2024.02.13-Maintenance-window-59.md) it is still pinned. During the same Tuesday, few hours later (according to Thunderbird, my RSS client), the title of the [🔥️ Issue - Git (forgejo) instance is down! 🔥️](https://status.disroot.org/issues/2023-12-13-forgejo-issue/) incident was updated to '[Resolved] 🔥 Issue - Git (forgejo) instance is down! 🔥' (more precisely a new RSS item was created). But on status.disroot.org the title is still the old one and the issue is now pinned; while the [corresponding git file](https://git.disroot.org/Disroot/cstate-content/raw/branch/main/issues/2023-12-13-forgejo-issue.md) was last updated in December. Is it possible that you have some local changes that were not pushed? While describing this issue I also realized that it can be my fault, since I pushed a wording fix for maintenance window 59 and it might have caused a merge conflict on your side.

muppeth commented

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

Owner

Yeah its a mess but we were few days ago talking with @meaz whether to move to kuma for status page. it was a contender when we were picking replacement for cachet but because of js use we went for cstate. However, kuma is more widely used and unlike cstate also shows current status of the service so it does not rely on us updating it manually which in case of issue is not something you prioritize on (you want to resolve the issue). So apart from being able to send annoucements or in case of longer downtime send extra information, people will be able to view status of the service in realtime. Thanks for reminding me about it as I was suppose to make issue on git #802

I think this resolves the issue as we will be replacing the system fairly soon, so I think this could be closed.

floss4good commented

2024-03-06 12:59:07 +01:00

Author

Indeed, when you have issues with services that are unavailable or performing bad, you shouldn't have to waste time and energy with manual updates for a status page.

I think this resolves the issue as we will be replacing the system fairly soon, so I think this could be closed.

Of course, if you will replace cState this ticket is becoming obsolete.

BTW: If you liked Cachet more that cState, I've recently learned that the original developer of Cachet has bought it back and started to rebuild it with different technologies; there is already a v3.x Demo

Indeed, when you have issues with services that are unavailable or performing bad, you shouldn't have to waste time and energy with manual updates for a status page. > I think this resolves the issue as we will be replacing the system fairly soon, so I think this could be closed. Of course, if you will replace cState this ticket is becoming obsolete. --- BTW: If you liked Cachet more that cState, I've recently learned that the original developer of Cachet has bought it back and started to rebuild it with different technologies; there is already a [v3.x Demo](https://v3.cachethq.io)