Plan – Cron jobs in Python

Re:Plan – Cron jobs in Python by chhantyal on Wednesday June 11, 2014 @05:40AM (#7877126)

And if you are already using Celery, it has crontab feature http://celery.readthedocs.org/en/latest/userguide/periodic-t...

[ Parent | on HN ]

Re:Plan – Cron jobs in Python by jocmeh on Wednesday June 11, 2014 @06:13AM (#7877182)

Yeah, we are using that as well. It's nice because it hooks up to your Django admin and people with the right permissions can reschedule stuff.

I don't see any use case for Plan, it's just complicating an easy task.

[ Parent | on HN ]

Re:Plan – Cron jobs in Python by gtuckerkellogg on Wednesday June 11, 2014 @07:34AM (#7877413)

I can see one use case for this family of tools: if the same script could generate either crontab files or launchd agents, so it could generate scheduling files for MacOSX, where crontab is discouraged.

[ Parent | on HN ]

Re:Plan – Cron jobs in Python by falcolas on Wednesday June 11, 2014 @11:00AM (#7878323)

MacOSX uses launchd as its crontab, but it retains the crontab interface.

[ Parent | on HN ]

Re:Plan – Cron jobs in Python by crdoconnor on Wednesday June 11, 2014 @10:30AM (#7878162)

Celery beat is pretty much exactly the same thing as cron except it's another service to configure and worry about keeping up and running. And it uses 35 MB of RAM instead of...well, I guess cron uses a few kilobytes.

I can't see the point of it at all.

When I want to kick off celery tasks I just have a cron job execute a django shell command.

[ Parent | on HN ]

Re:Plan – Cron jobs in Python by icebraining on Wednesday June 11, 2014 @06:20PM (#7880767)

I guess cron uses a few kilobytes.

A full megabyte on my machine, actually! Still a long way from 35MBs, though.

[ Parent | on HN ]