2020-12-04 23:13

beat_schedule_filename is created even if Django is selected.

Hi there,

It appears that the BEAT_SCHEDULE_FILENAME is still created even if django-celery-beat is used. It doesn't appear to be used (based on timestamp changing) but it is still created.

Low priority but it is confusing to tell whether it's using the django database or not.

FYI - I'm launching this in my test env as follows.

celery -A celery_app worker --events --beat -S django -l DEBUG

This command is in alignment with the docs and it makes sense that it creates the django.db as the -S option defines the filename.

To verify that its working I needed to set BEAT_SYNC_EVERY = 1 and then watch the Django database.


  • 点赞
  • 回答
  • 收藏
  • 复制链接分享