Last 30 days
-
-
-
Install (How to install django-cron) Wiki page commented on by rviotti
-
Older
-
-
-
-
-
-
r32
(fixed bug 21 (google code) Cron jobs can now be on a timesca...) committed by Jim.mixt...@gmail.com
- fixed bug 21 (google code) Cron jobs can now be on a timescale greater than 1 day
it seems bespin has a strange idea of tabs... fixed
fixed bug 21 (google code) Cron jobs can now be on a timescale greater than 1 day
it seems bespin has a strange idea of tabs... fixed
-
FAQ
(A few common questions) Wiki page edited by Jim.mixt...@gmail.com
- Revision r31
Edited wiki page through web user interface.
Revision r31
Edited wiki page through web user interface.
-
FAQ
(A few common questions) Wiki page edited by Jim.mixt...@gmail.com
- Revision r30
Edited wiki page through web user interface.
Revision r30
Edited wiki page through web user interface.
-
FAQ
(A few common questions) Wiki page edited by Jim.mixt...@gmail.com
- Revision r29
Edited wiki page through web user interface.
Revision r29
Edited wiki page through web user interface.
-
FAQ
(A few common questions) Wiki page edited by Jim.mixt...@gmail.com
- Revision r28
Edited wiki page through web user interface.
Revision r28
Edited wiki page through web user interface.
-
FAQ
(A few common questions) Wiki page added by Jim.mixt...@gmail.com
- Revision r27
Created wiki page through web user interface.
Revision r27
Created wiki page through web user interface.
-
-
-
-
issue 4
(simple enhancement: run cronjobs from management.py) commented on by andybak
-
-
issue 4
(simple enhancement: run cronjobs from management.py) commented on by andybak
-
-
-
issue 4
(simple enhancement: run cronjobs from management.py) commented on by andybak
-
-
-
-
-
-
-
-
-
r25
(removed the code that deletes old jobs... it's no longer nec...) committed by Jim.mixt...@gmail.com
- removed the code that deletes old jobs... it's no longer necessary because the "last run time" is
stored in the DB. We can just check that for any jobs instead of blindly clearing all the jobs on
init
removed the code that deletes old jobs... it's no longer necessary because the "last run time" is
stored in the DB. We can just check that for any jobs instead of blindly clearing all the jobs on
init
-
r24
(fixed issues with breaking the queue when debugging
) committed by Jim.mixt...@gmail.com
- fixed issues with breaking the queue when debugging
fixed issues with breaking the queue when debugging
-
-
-
-
issue 11
(Syncdb exits on fresh install while executing base.py) commented on by whit537
-
-
issue 16
(syncdb table creation fails using postgresql + psycopg2) commented on by nbvFOUR
-
-
-
issue 16
(syncdb table creation fails using postgresql + psycopg2) commented on by ninethval
-
-
-
-
issue 18
(returned more than one Job ( cronScheduler.register(TimedRot...) commented on by gnugit
-
-
issue 18
(returned more than one Job ( cronScheduler.register(TimedRot...) reported by gnugit
-
-
issue 4
(simple enhancement: run cronjobs from management.py) commented on by theMichaek
-
-
issue 4
(simple enhancement: run cronjobs from management.py) commented on by theMichaek
-
-
issue 4
(simple enhancement: run cronjobs from management.py) commented on by theMichaek
-
-
-
issue 16
(syncdb table creation fails using postgresql + psycopg2) Status changed by Jim.mixtake
-
-
issue 16
(syncdb table creation fails using postgresql + psycopg2) commented on by Jim.mixtake
-
-
-
issue 16
(syncdb table creation fails using postgresql + psycopg2) commented on by rcatherman
-
-
|