Cachet - status page system
-
-
wrote on Jun 19, 2018, 8:51 PM last edited by
I would second this!
-
wrote on Jun 21, 2018, 4:27 PM last edited by
Source
https://github.com/CachetHQ/CachetOpen Source Self-Hosted Cachet Alternatives
https://alternativeto.net/software/cachet/?license=opensource&platform=self-hosted -
wrote on Aug 6, 2018, 2:06 PM last edited by
This would make me sign up to Cloudron
-
wrote on Jun 19, 2019, 7:19 PM last edited by
Would love to see this as well.
-
wrote on Jul 11, 2019, 7:21 AM last edited by
Are we able to workaround this not being a Cloudron-approved app by deploying Cachet in a LAMP app instead? Has anyone tried that yet? I think I may try that this weekend if time permits.
-
I built this a few months ago including a python script to check the uptime for websites, but I've lost the repo while moving to a new docker registry. There should be a backup somewhere which I can check... However, there should be no problem installing it on a LAMP.
-
Wanted to provide an update on this. Packaging this app is straightforward since it's lavarel based (https://git.cloudron.io/cloudron/cachethq-app). There are some issues:
- The 2.3 release does not support php 7.2. https://github.com/CachetHQ/Cachet/issues/3719 . So, let's wait for the 2.4 release.
- I found the app itself does not monitor. One has to install sidecar package like https://github.com/castawaylabs/cachet-monitor or https://github.com/mtakaki/cachet-url-monitor . I guess we need to bundle one of these solutions in the package itself.
-
Wanted to provide an update on this. Packaging this app is straightforward since it's lavarel based (https://git.cloudron.io/cloudron/cachethq-app). There are some issues:
- The 2.3 release does not support php 7.2. https://github.com/CachetHQ/Cachet/issues/3719 . So, let's wait for the 2.4 release.
- I found the app itself does not monitor. One has to install sidecar package like https://github.com/castawaylabs/cachet-monitor or https://github.com/mtakaki/cachet-url-monitor . I guess we need to bundle one of these solutions in the package itself.
-
Wanted to provide an update on this. Packaging this app is straightforward since it's lavarel based (https://git.cloudron.io/cloudron/cachethq-app). There are some issues:
- The 2.3 release does not support php 7.2. https://github.com/CachetHQ/Cachet/issues/3719 . So, let's wait for the 2.4 release.
- I found the app itself does not monitor. One has to install sidecar package like https://github.com/castawaylabs/cachet-monitor or https://github.com/mtakaki/cachet-url-monitor . I guess we need to bundle one of these solutions in the package itself.
-
@girish is it possible to pack this in an unstable release or help me install it on cloudron?
wrote on Apr 8, 2020, 5:08 PM last edited by@Trankery As @girish mentioned, there are some limitations in it currently with support for php and so it was suggested to wait for the 2.4 version of Cachet, however 2.4 does not appear to have been released yet officially by the CachetHQ team. You can theoretically deploy a LAMP stack and deploy the app that way as discussed earlier in the thread. I have been meaning to try deploying this myself as well and haven't completed it. Maybe I'll do that in the next week or two, and will report back if I can get it to work. At this time though, I'm almost looking at alternatives to Cachet to provide service status updates and monitoring history to my clients.
-
@Trankery As @girish mentioned, there are some limitations in it currently with support for php and so it was suggested to wait for the 2.4 version of Cachet, however 2.4 does not appear to have been released yet officially by the CachetHQ team. You can theoretically deploy a LAMP stack and deploy the app that way as discussed earlier in the thread. I have been meaning to try deploying this myself as well and haven't completed it. Maybe I'll do that in the next week or two, and will report back if I can get it to work. At this time though, I'm almost looking at alternatives to Cachet to provide service status updates and monitoring history to my clients.
wrote on Apr 8, 2020, 5:43 PM last edited bySide note: A useful resource for alternatives in case this helps your project @Trankery: https://github.com/ivbeg/awesome-status-pages - In particular I think https://pagefate.com/ looks quite good.
-
-
Actually, I think we should wait for the 2.4 release - https://github.com/CachetHQ/Cachet/issues/3968 . If there is another status page system, we can look into packaging that.
-
Actually, I think we should wait for the 2.4 release - https://github.com/CachetHQ/Cachet/issues/3968 . If there is another status page system, we can look into packaging that.
wrote on Apr 8, 2020, 8:51 PM last edited by@girish - Definitely lots of alternatives. I think the more common ones to Cachet is StatPing, Staytus (although apparently it's discontinued but not too old), a newer one called Statusfy, list goes on. I'm going to try to package together one someday as well as a custom app and see how it goes.
--
Dustin Dauncey
www.d19.ca -
Actually, I think we should wait for the 2.4 release - https://github.com/CachetHQ/Cachet/issues/3968 . If there is another status page system, we can look into packaging that.
wrote on Apr 8, 2020, 11:59 PM last edited by@girish said in Cachet - status page system:
Actually, I think we should wait for the 2.4 release - https://github.com/CachetHQ/Cachet/issues/3968 . If there is another status page system, we can look into packaging that.
After a quick research, I found the following: https://github.com/bazzite/statusfy
No idea if this fits the bill though.
-
wrote on Apr 9, 2020, 7:41 AM last edited by
Open Source Self-Hosted Cachet Alternatives
https://alternativeto.net/software/cachet/?license=opensource&platform=self-hosted -
wrote on Apr 11, 2020, 11:40 PM last edited by
Staytus would be amazing to have.
-
-
@Trankery From what I can tell, staytus hasn't been developed in a while (last commit almost a year ago). CachetHQ is active but hasn't release in a while as well (https://github.com/CachetHQ/Cachet/issues/3968). I am waiting for some upstream response before publishing it because don't want people using apps that are not actively maintained.
