Cachet: Still Active?

[the-maldridge]

Normally, I'd send a poke like this to an email or a chat room, but seeing as the chat bubble on the website spins and doesn't connect, and most other things pointed to twitter I'll ask here.

Is this project still active? At almost 11k stars on github its clear people think this project is one of the better if not the best status pages available. I'm inclined to agree, but I'm hesitant to actually use this given that there's over 3.5k commits on an unreleased branch, and that branch still has some pretty basic errors in it (username is displayed as :username for example in status updates). There's also a majority of pull requests opened by the dependabot for security updates that haven't been merged.

I also see there's a patreon, and the last updates appear to be years ago.

I really want to like this project, because the alternative right now seems to be starting from scratch and re-implementing a lot of the functionality, something I suspect is a bottomless well of nuance.

Looking forward to any signs of life.

[welcome[bot]]

:wave: Thank you for opening your first issue. I'm just an automated bot that's here to help you get the information you need quicker, so please ignore this message if it doesn't apply to your issue.
If you're looking for support, you should try the Slack group by registering your email address at https://cachethq-slack.herokuapp.com. Alternatively, email [email protected] for our Professional support service (please note, this a paid service.)
If you're issue is with documentation, you can suggest edits by clicking the Suggest Edits link on any page, or open an issue at https://github.com/CachetHQ/Docs

[NHRedAnt]

Glad to see this post, it's exactly what I'm wondering myself. I wish I could give you an answer but I've found out about this project this morning.

[jbrooksuk]

Hey guys! I'm still maintaining Cachet support in the background.

I really need to get my teeth into the next release, but I could do with some help if I'm honest!

[NHRedAnt]

Glad to hear your still around AND the honesty. I'm not sure how deep I'll get into this project or what help I could provide. This tool is been setup at our University to expose the status of services we depend on.

I've taken on the task of collecting service status and updating Cachet. I'll be working in python, and testing that API. I suspect at some point I'll do a container test in podman. I'll certainly report back anything I find.

If you have concerns in areas that I might hit on my quest, I would be happy to test a little harder around areas of your choosing.

Thanks again for the response! Hope something I end up doing proves useful to your efforts.

[the-maldridge]

I built from master and things seemed reasonably OK, albeit with a number of small frontend bugs.

I have access to an IdP and would be happy to test/debug SAML integration if that's still on the docket for the next release. I personally don't touch PHP anymore as a dev, but I can reach out to folks that are looking for a project at the moment and point them this way.

[NHRedAnt]

During my testing I've very repeatably caused a number of internal server error 500 bugs around incident updates (using the python3 API). As previously noted I'm not PHP savvy.

I was able to deploy the provided docker container on podman, and expect to contribute back those instructions.

One thing I do not yet understand is where the PHP 500 errors get logged. The container logs don't see anything more than the http logs result code. I'm interested in finding those logs to be able to better report/fix issues. Is there anything documenting how to collect information for a bug report?

[jbrooksuk]

You should use the 2.4 branch over master.

I have also started a 3.x branch which works on the new design and rewriting of most code.

[robcxyz]

@jbrooksuk Is there a road map for 3.x features in development?

[jbrooksuk]

I'm afraid not. It's very much a case of getting the design implemented, ripping out old code and getting some new features in.

The new design is the most important step though. We need a new design for proper incident updates and a better dashboard.

The dashboard will be overhauled to use the API instead of essentially a copy of the functionality.

Any help would be appreciated!

[thomvaill]

What do you advise for a new deployment of Cachet with Docker?

• Use latest Docker image (v2.3.15)
• Build my own v2.4 Docker image

I see that a lot of bugs were fixed in 2.4 and new features too, so I really want to use 2.4 but since there's no release, nor stable Docker image I am a bit afraid!

[vRobM]

Can we get an update on this?