1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
|
"""myapp.py
Usage::
# The worker service reacts to messages by executing tasks.
(window1)$ python myapp.py worker -l INFO
# The beat service sends messages at scheduled intervals.
(window2)$ python myapp.py beat -l INFO
# XXX To diagnose problems use -l debug:
(window2)$ python myapp.py beat -l debug
# XXX XXX To diagnose calculated runtimes use C_REMDEBUG envvar:
(window2) $ C_REMDEBUG=1 python myapp.py beat -l debug
You can also specify the app to use with the `celery` command,
using the `-A` / `--app` option::
$ celery -A myapp worker -l INFO
With the `-A myproj` argument the program will search for an app
instance in the module ``myproj``. You can also specify an explicit
name using the fully qualified form::
$ celery -A myapp:app worker -l INFO
"""
from celery import Celery
app = Celery(
# XXX The below 'myapp' is the name of this module, for generating
# task names when executed as __main__.
'myapp',
broker='amqp://guest@localhost//',
# ## add result backend here if needed.
# backend='rpc'
)
app.conf.timezone = 'UTC'
@app.task
def say(what):
print(what)
@app.on_after_configure.connect
def setup_periodic_tasks(sender, **kwargs):
# Calls say('hello') every 10 seconds.
sender.add_periodic_task(10.0, say.s('hello'), name='add every 10')
# See periodic tasks user guide for more examples:
# https://docs.celeryq.dev/en/latest/userguide/periodic-tasks.html
if __name__ == '__main__':
app.start()
|
