fork/django-q2
1
0
Fork 0
mirror of https://github.com/django-q2/django-q2.git synced 2026-10-01 14:48:12 +08:00
Code Issues Packages Projects Releases Wiki Activity

added schedule to README

Browse Source
This commit is contained in:
Ilan Steemers
2015-06-25 20:30:13 +02:00
parent d5d529f874
commit e2f7f1e5bf
4 changed files with 29 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+8 -1
View File
@@ -31,8 +31,15 @@ You can monitor basic information about all the connected clusters by running `
![qmonitor command](http://i.imgur.com/5cm7hdP.png)
###Admin integration
Django Q registers itself with the admin page to show failed and successful tasks.
Django Q registers itself with the admin page to show failed, successful and scheduled tasks.
From there task results can be read or deleted. If necessary, failed tasks can be reintroduced to the queue.
Schedules be created and their results monitored.
![q admin](http://i.imgur.com/WTZkW9r.png)
###Schedules
Scheduled tasks are a django model and can be created through the admin interface or by creating a Schedule instance directly.
Like the Async Task, a Schedule can take an optional hook keyword and is used as a template to create the actual task package at the scheduled time.
If a result task is available in the database, it can be accessed through the Schedule instance's `result()` method.
### Signed Tasks
Tasks are first pickled to Json and then signed using Django's own signing module before being sent to a Redis list. This ensures that task packages on the Redis server can only be excuted and read by clusters and django servers who share the same secret key.