New state page?

muppeth commented

2021-11-03 10:59:44 +01:00

Owner

I would like to migrate our current cachet site which is not very maintained to something a bit more sleek and with more options such as monitoring uptime like robotuptime etc.

https://github.com/louislam/uptime-kuma

Any ideas?

I would like to migrate our current cachet site which is not very maintained to something a bit more sleek and with more options such as monitoring uptime like robotuptime etc. https://github.com/louislam/uptime-kuma Any ideas?

muppeth added the

Discussion

label 2021-11-03 10:59:44 +01:00

muppeth self-assigned this 2021-11-03 10:59:44 +01:00

meaz was assigned by muppeth

2021-11-03 10:59:44 +01:00

fede was assigned by muppeth

2021-11-03 10:59:44 +01:00

antilopa was assigned by muppeth

2021-11-03 10:59:44 +01:00

avg_joe was assigned by muppeth

2021-11-03 10:59:44 +01:00

muppeth commented

2021-11-03 11:04:40 +01:00

Author

Owner

Or https://github.com/cstate/cstate

meaz commented

2021-11-03 11:50:02 +01:00

Owner

It looks like kuma has a bit more features.

fede commented

2021-11-03 15:04:30 +01:00

Owner

Kuma looks more neat and feature rich. Cstate looks like Cachet (the one we're using now).

antilopa commented

2021-11-04 12:25:12 +01:00

Owner

agree with these conclusions. shall we try Kuma then?

muppeth commented

2021-11-04 12:46:13 +01:00

Author

Owner

Kuma comes wiht a price to pay though. JS. Not sure about cstate as I haven't look into it. I could setup both so we could test a bit and see if we like it or if we just make something from scratch and simple. i am looking at a way to integrate also with searx and, lets not forget, disroot android app too.

fede commented

2021-11-05 02:37:34 +01:00

Owner

What would be the problem of using JS? I know many people don't "like it" or say it's not a cool language, but I'm not sure if those claims are made on solid ground.

meaz commented

2022-05-08 09:52:26 +02:00

Owner

So so... Do we test Kuma then?

muppeth commented

2022-05-09 11:36:56 +02:00

Author

Owner

I think I will dpeloy both and perhaps find a third one to test a bit. The thing with JS @fede is that often it's not needed and you can't forget about browser not supporting it or users having it disabled. I think to be able to just see if service is up or down or if there is any known issues or maintenance, we shouldn't require js. However if the amount of features we need is far superior to others I would go for it.

So yeah, will play around with some and write up a small summary.

I think I will dpeloy both and perhaps find a third one to test a bit. The thing with JS @fede is that often it's not needed and you can't forget about browser not supporting it or users having it disabled. I think to be able to just see if service is up or down or if there is any known issues or maintenance, we shouldn't require js. However if the amount of features we need is far superior to others I would go for it. So yeah, will play around with some and write up a small summary.

muppeth commented

2022-05-11 00:07:24 +02:00

Author

Owner

I did some comparison form all kind of available status pages (btw. I think we should chage the url to status.disroot.org) and indeed uptime-kuma looks like the best solution. Although heavily JS based (most of them are) it also provies notifications that aren't possible with other ones, like email or xmpp etc. It will make the migration easy and people that do use email for notifs, could use. I think I will write ansible role for it and deploy as status.disroot.org then ping massimiliano to adjust API calls in disroot mobile app to use new status page.

👍 1 🚀 1

meaz added a new dependency 2022-05-24 22:13:27 +02:00

#73 reactivate bot in state@chat.disroot.org

muppeth commented

2022-05-27 13:37:54 +02:00

Author

Owner

I have created a role for kuma as I think we are planning to go this route, but one thing I noticed is that there is no way to subscribe to alerts via email. Cstate also doesnt have that option (only rss).

Kuma however allows to post to various places, which include email, xmpp, matrix,etc.

One way to do it would be to instead of relying on kuma to send issue updates, we could make a central script to do it. In that way we could introduce an option in user.disroot.org where people could subscribe to get updates on state via email, and with a single script we could post issue info or deployment messages to: email subscribers, xmpp,fedi, kuma etc. This operation is anyway manual anyway so shouldn't matter much. That would allow us to be independent of kuma (or any other status page in the future) and implement more disroot suitable status update notification (on main website or nextlcoud or as bar on affected services etc).

I have created a role for kuma as I think we are planning to go this route, but one thing I noticed is that there is no way to subscribe to alerts via email. Cstate also doesnt have that option (only rss). Kuma however allows to post to various places, which include email, xmpp, matrix,etc. One way to do it would be to instead of relying on kuma to send issue updates, we could make a central script to do it. In that way we could introduce an option in user.disroot.org where people could subscribe to get updates on state via email, and with a single script we could post issue info or deployment messages to: email subscribers, xmpp,fedi, kuma etc. This operation is anyway manual anyway so shouldn't matter much. That would allow us to be independent of kuma (or any other status page in the future) and implement more disroot suitable status update notification (on main website or nextlcoud or as bar on affected services etc).

muppeth commented

2022-05-27 13:55:54 +02:00

Author

Owner

Hmmm.... playing around with Kuma more and more the less and less I like it.

Kuma allows only for one incident/issue to be pinned. This means the main feature we used so far will be deleted, which is History. So apart form fancy UI, people wont be able to see the past incidents, which I think is the best thing about such status page. I think I would therefore go with c-state. check for example https://status.snopyta.org

Hmmm.... playing around with Kuma more and more the less and less I like it. Kuma allows only for one incident/issue to be pinned. This means the main feature we used so far will be deleted, which is History. So apart form fancy UI, people wont be able to see the past incidents, which I think is the best thing about such status page. I think I would therefore go with c-state. check for example https://status.snopyta.org

muppeth added this to the 06.22 - June milestone 2022-05-27 14:05:59 +02:00

meaz commented

2022-05-28 10:03:07 +02:00

Owner

cstate is fine with me then.