Use Supervisor instead of Docker for Celery services
Closed this issue · 1 comments
mrosendin commented
Description
Currently the Celery worker and beat services are started in the Docker Compose file. We should remove those services and start Celery with Supervisor instead (see my Adobe project for a full example). An example supervisord.conf file shown below:
[supervisord]
nodaemon=true
[program:python]
stdout_logfile=/dev/stdout
stdout_logfile_maxbytes=0
stderr_logfile=/dev/stderr
stderr_logfile_maxbytes=0
command=flask run --host=0.0.0.0
[program:celery]
stdout_logfile=/dev/stdout
stdout_logfile_maxbytes=0
stderr_logfile=/dev/stderr
stderr_logfile_maxbytes=0
command=celery -A app.celery worker -E -l info
[program:docs]
stdout_logfile=/dev/stdout
stdout_logfile_maxbytes=0
stderr_logfile=/dev/stderr
stderr_logfile_maxbytes=0
command=mkdocs serve --dev-addr=0.0.0.0:8000