sosedoff

Not sure what kind of issues you're having with search, but it's pretty straightforward to browse table data with a filter on a single column (be it numerical or text data). Im the author - shoot me an email (in profile) if you have any questions.

I dont think there's any competition with Google here, CronRunner is tailored specifically for Heroku.

There is no dependency graph between the jobs, i think this would be the case for a specialized tool. Cronrunner is very simple when it comes to job definition.

As for cron jobs, there's a bit of validation involved. The jobs are not executed with the old cron daemon, im using cron-like implementation in my stack. The logs are produces by Heroku platform so im just saving those, no magic at all.

Hi HN,

This is a small project that i've been meaning to launch for quite some time. Cronrunner is a job scheduler addon for Heroku applications, similar to standard scheduler but more powerful: you can define jobs with cron, set timezone, see history and receive error notifications. No need to setup webhooks or background jobs.

I've been using this addon internally for many months and finally decided to clean up and make a public site. The addon is not listed on the marketplace yet, i just need a bunch of test users to try it out, once it's done i can move it to the beta phase.

Feedback/ideas are highly appreciated!

Not sure if something is broken, but after i created a codemason server i cant delete it - there's no button to do that.

There are a few issues and PRs that i opened myself, but aside from that there weren't many contributions from other developers. I can't really say the project is under active development, but it's definitely useful enough, at lease for my use cases.

For anyone wondering what this is: it's tool to build flows like "git push to X". I've built a few internal tools that use this package, mostly for deployment purposes similar to Heroku (but based on Docker).

The toolkit consists of 2 pieces: the server (http/ssh based) and push receiver. The server component provides the git repository endpoint and permission handling, and the receiver piece allows to setup the logic flow, like what to do with the push and ability to read the push tree structure and run some commands against it.

I've created this package some time ago, but decided to post just now, maybe someone will find it useful.

Thanks!