Healthchecks.io -- Cron job monitoring

[Lanhild]

@Kubernetes I might take a quick look at it. Not sure I'll go very far, but I can contribute some notes/remarks at the least

[Lanhild]

Had been pretty busy with work, but I looked a bit at the software today.
Here's a small list of notes;

We don't need the SMTP integration yet as the webhooks are sufficient to get it working.

SMTP could be used for logging in, as there is the possibility of sending a "magic email link" for the login process.

postgres addon is indeed needed as the application database.

Everything related to configuration is managed through environment variables.

I've noticed that an initial superuser needs to be created. Not sure if it can be created directly through the app's UI, but otherwise a script in the code is provided for this specific purpose.

As for the actual startup process, I'm not sure how we can do it. It seems like uwsgi is used to start the server part of the application and run migrations, etc.

[Lanhild]

I've started a package, not sure I'll be able to go further than that though. Anyway, so far I've managed to get the UI up and running, but there is an error with the database connection.

https://github.com/Lanhild/healthchecks-cloudron

Don't hesitate to ask if there's any questions/needs

[Lanhild]

@Lanhild You might need to chmod +x the start script manually

[Kubernetes]

@Lanhild Thank your very much for your efforts! Great work what you have done. I see that you replaced the critical paths directly in the source. Not sure if that might become a problem in future releases. Probably it would be easier to use symlinks instead of replacing the paths in the source.

When you chmod +x start.sh before packaging the execution bit should be make it into the docker image. If you do

RUN chmod +x start.sh

in your Dockerfile right after you COPY it, it should work, too.

[threetrees3]

Just wanted to give a bump for visibility and thank the contributors for getting things going for Healthchecks!

Unfortunately, am not able to contribute in the code wise

[neoplex]

@threetrees3 said in Healthchecks.io -- Cron job monitoring:

Just wanted to give a bump for visibility and thank the contributors for getting things going for Healthchecks!

Unfortunately, am not able to contribute in the code wise

Same here, having healthchecks as an app would be awesome! I've got a few instances I am looking to migrate plus, this would make it super easy to spin up dedicated customer instances as needed

Thanks for all the great work!

[michaelpope]

@neoplex Just as a heads up, I believe Uptime Kuma does a lot of the same stuff. If you're looking for something they currently have on Cloudron right now (there is not an import tool though...)

[neoplex]

@michaelpope Uptime Kuma caters to a completely different use case, although, there is some overlap e.g. webhook reporting and notification. I am running several instances of both, Uptime Kuma and healthchecks in production

[neoplex]

Shameless follow up

[neoplex]

Has anyone worked on this in silence? If not, will port it

@girish This is as simple as smokeping in terms of implementation. Generally, are you guys interested to move it to the appstore, once tested and stable? Otherwise we'll package it as a community app and set up a build pipe.

[timconsidine]

@neoplex I'm tempted to say that packaging it as a community app is not a separate approach to AppStore, it's a stage along the road. Getting it in use by Cloudron users via a Community App builds the case for it to be adopted in the AppStore.

Just my opinion.

[girish]

Yes, if there is broad community interest in the app, we will work with the community app packager and try to get it into the App Store. In the meantime, community apps are a great way to have a package that you have a need for available and tested by others.