uptick/bronski

bronski's Issues

Badge it up

Chuck in at least a pypi badge so we can see latest version at a glance and have a quick link to pypi?

Scheduling quirk when updating in admin.

If I change cron string in admin to * * * * *, it'll start immediately getting picked up and running every minute. But if I try to be any more specific (eg setting minute to just a couple mins after current time), it won't run. Could be related to either #2 or #3, but even trying 25 * * * * when the time was 1:19PM, didn't result in Job getting picked up. I tried setting the last_run time to waay in the past, just in case the system thought it had already run recently and didn't want to run again, but no dice.

Jobs running in wrong timezone.

Jobs seem to run in wrong timezone. I schedule for 4AM, job runs at 2PM.

`last_run` displays as 1min prior to scheduled.

Job last_run shows that they run one minute prior to when they're scheduled. So, actually, when I schedule for 4AM, it says it last ran at 1:59PM.

Use a Swappable Model for CRONTAB_MODEL

This is the same pattern used by django.contrib.auth (settings.AUTH_USER_MODEL), and I also implemented it for django-occupation.

https://bitbucket.org/schinckel/django-occupation/src/default/src/occupation/models.py

I also implemented a helper function for getting the model:

https://bitbucket.org/schinckel/django-occupation/src/f1ac9d05e3de436ec786cfe608ba5f15149589a0/src/occupation/utils.py#lines-17

It's been a while, but I think that was the same pattern used by d.c.a