* This is EXACTLY how you should make a README file for a tool/project, especially on Github. Every project needs to take after this example before they register a domain and create an HTML5 splash page.
* Thank you so much for using existing tools and not building a new cron or transport protocol from scratch. Now I know this builds on top of reliable tools.
* Would it be difficult to remove the web sockets requirement? Orgs with old, non-replaceable web servers/proxies, or old network appliances with layer7 proxies, might find this handy but not be able to support web sockets.
* Instead of a 'DROP TABLE', why not a 'CREATE TABLE IF NOT EXISTS' ? (In my own projects I usually make all the database table/column names into static variables at the top of my code, so people can modify them if they want) Still, it's nice of you to include a tool that modifies/verifies the db automatically.
* Kinda off topic: I just wrote an open-source replacement for Dead Man's Snitch, an out of bound alerting tool intended to be used by cron. If you want I can share the source so you can either use it, or create your own implementation that works with a remote copy of minicron?
1. Thanks, I put a lot of effort into the README :)
2. That was one of my aims really, cron is a great tool it's just missing a few things that hopefully this can fill.
3. I was thinking about this recently actually, I don't see why I couldn't add a config option that toggles between WebSockets and HTTP(s) for the transport of data to/from the hub. I did a bit of research into WebSockets when I was planning this and from what I understand they put a lot of effort into making sure it would work behind proxies/firewalls etc but I can't remember the exact specifics.
4. That SQL actually comes from ActiveRecord (`rake db:setup`) so I don't have any direct control over it. Long term I want to add proper migrations.
5. If it has an API of some kind I don't see why it couldn't be added as an alerting option alongside email, sms and pagerduty.
Comments
This looks really cool! Couple of comments:
* This is EXACTLY how you should make a README file for a tool/project, especially on Github. Every project needs to take after this example before they register a domain and create an HTML5 splash page.
* Thank you so much for using existing tools and not building a new cron or transport protocol from scratch. Now I know this builds on top of reliable tools.
* Would it be difficult to remove the web sockets requirement? Orgs with old, non-replaceable web servers/proxies, or old network appliances with layer7 proxies, might find this handy but not be able to support web sockets.
* Instead of a 'DROP TABLE', why not a 'CREATE TABLE IF NOT EXISTS' ? (In my own projects I usually make all the database table/column names into static variables at the top of my code, so people can modify them if they want) Still, it's nice of you to include a tool that modifies/verifies the db automatically.
* Kinda off topic: I just wrote an open-source replacement for Dead Man's Snitch, an out of bound alerting tool intended to be used by cron. If you want I can share the source so you can either use it, or create your own implementation that works with a remote copy of minicron?
1. Thanks, I put a lot of effort into the README :)
2. That was one of my aims really, cron is a great tool it's just missing a few things that hopefully this can fill.
3. I was thinking about this recently actually, I don't see why I couldn't add a config option that toggles between WebSockets and HTTP(s) for the transport of data to/from the hub. I did a bit of research into WebSockets when I was planning this and from what I understand they put a lot of effort into making sure it would work behind proxies/firewalls etc but I can't remember the exact specifics.
4. That SQL actually comes from ActiveRecord (`rake db:setup`) so I don't have any direct control over it. Long term I want to add proper migrations.
5. If it has an API of some kind I don't see why it couldn't be added as an alerting option alongside email, sms and pagerduty.
Thanks for your feedback!