fix: use LOG_LEVEL for celery startup (#7628)

langgenius · Aug 26, 2024 · 8dfdb37 · 8dfdb37
1 parent 17fd773
commit 8dfdb37
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/api/docker/entrypoint.sh b/api/docker/entrypoint.sh
@@ -20,11 +20,11 @@ if [[ "${MODE}" == "worker" ]]; then
     CONCURRENCY_OPTION="-c ${CELERY_WORKER_AMOUNT:-1}"
   fi
 
-  exec celery -A app.celery worker -P ${CELERY_WORKER_CLASS:-gevent} $CONCURRENCY_OPTION --loglevel INFO \
+  exec celery -A app.celery worker -P ${CELERY_WORKER_CLASS:-gevent} $CONCURRENCY_OPTION --loglevel ${LOG_LEVEL} \
     -Q ${CELERY_QUEUES:-dataset,generation,mail,ops_trace,app_deletion}
 
 elif [[ "${MODE}" == "beat" ]]; then
-  exec celery -A app.celery beat --loglevel INFO
+  exec celery -A app.celery beat --loglevel ${LOG_LEVEL}
 else
   if [[ "${DEBUG}" == "true" ]]; then
     exec flask run --host=${DIFY_BIND_ADDRESS:-0.0.0.0} --port=${DIFY_PORT:-5001} --debug