From b85ef5cfa52f05fde1386c81db9d257cbd9e23cd Mon Sep 17 00:00:00 2001 From: Bruno Alla Date: Sat, 25 Feb 2023 12:01:17 +0000 Subject: [PATCH] Extend explanations for celery beat --- {{cookiecutter.project_slug}}/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/{{cookiecutter.project_slug}}/README.md b/{{cookiecutter.project_slug}}/README.md index e66831451..83f9a7e48 100644 --- a/{{cookiecutter.project_slug}}/README.md +++ b/{{cookiecutter.project_slug}}/README.md @@ -63,14 +63,14 @@ celery -A config.celery_app worker -l info Please note: For Celery's import magic to work, it is important *where* the celery commands are run. If you are in the same folder with *manage.py*, you should be right. -To run a celery beat: +To run [periodic tasks](https://docs.celeryq.dev/en/stable/userguide/periodic-tasks.html), you'll need to start the celery beat scheduler service. You can start it as a standalone process: ``` bash cd {{cookiecutter.project_slug}} celery -A config.celery_app beat ``` -or you can run worker with beat: +or you can embed the beat service inside a worker with the `-B` option (not recommended for production use): ``` bash cd {{cookiecutter.project_slug}}