WEBLATE_ADMIN_NAME, WEBLATE_ADMIN_EMAIL Number of processes and memory consumption The number of worker processes for both uWSGI and Celery is determined automatically based on number of CPUs. This works reducing number of workers: environment: WEBLATE_WORKERS: 2 You can also fine-tune individual worker categories: environment: UWSGI_WORKERS: 4 CELERY_MAIN_OPTIONS: --concurrency 2 CELERY_NOTIFY_OPTIONS: WEBLATE_ADDONS, INSTALLED_APPS Container settings WEBLATE_WORKERS New in version 4.6.1. Base number of worker processes running in the container. When not set it is determined automatically on container startup

WEBLATE_ADMIN_NAME, WEBLATE_ADMIN_EMAIL Number of processes and memory consumption The number of worker processes for both uWSGI and Celery is determined automatically based on number of CPUs. This works reducing number of workers: environment: WEBLATE_WORKERS: 2 You can also fine-tune individual worker categories: environment: UWSGI_WORKERS: 4 CELERY_MAIN_OPTIONS: --concurrency 2 CELERY_NOTIFY_OPTIONS: Weblate Manual, Release 4.7 Container settings WEBLATE_WORKERS New in version 4.6.1. Base number of worker processes running in the container. When not set it is determined automatically on container startup

WEBLATE_ADMIN_NAME, WEBLATE_ADMIN_EMAIL Number of processes and memory consumption The number of worker processes for both uWSGI and Celery is determined automatically based on number of CPUs. This works reducing number of workers: environment: WEBLATE_WORKERS: 2 You can also fine-tune individual worker categories: environment: UWSGI_WORKERS: 4 CELERY_MAIN_OPTIONS: --concurrency 2 CELERY_NOTIFY_OPTIONS: WEBLATE_ADDONS, INSTALLED_APPS Container settings WEBLATE_WORKERS New in version 4.6.1. Base number of worker processes running in the container. When not set it is determined automatically on container startup

CELERY_BROKER_URL = "memory://" CELERY_TASK_EAGER_PROPAGATES = True You should also start the Celery worker to process the tasks and start scheduled tasks, this can be done directly on the command line (which this line if you don't use an app CELERY_APP="weblate.utils" # Extra command-line arguments to the worker, # increase concurency if you get weblate.E019 CELERYD_OPTS="--beat:celery --queues:celery=celery CELERYD_LOG_LEVEL="INFO" # Internal Weblate variable to indicate we're running inside Celery CELERY_WORKER_RUNNING="1" Additional configuration to rotate Celery logs using logrotate to be placed as /etc/logrotate

CELERY_BROKER_URL = "memory://" CELERY_TASK_EAGER_PROPAGATES = True You should also start the Celery worker to process the tasks and start scheduled tasks, this can be done directly on the command line (which this line if you don't use an app CELERY_APP="weblate.utils" # Extra command-line arguments to the worker, # increase concurency if you get weblate.E019 CELERYD_OPTS="--beat:celery --queues:celery=celery CELERYD_LOG_LEVEL="INFO" # Internal Weblate variable to indicate we're running inside Celery CELERY_WORKER_RUNNING="1" Additional configuration to rotate Celery logs using logrotate to be placed as /etc/logrotate

CELERY_BROKER_URL = "memory://" CELERY_TASK_EAGER_PROPAGATES = True You should also start the Celery worker to process the tasks and start scheduled tasks, this can be done directly on the command line (which this line if you don't use an app CELERY_APP="weblate.utils" # Extra command-line arguments to the worker, # increase concurency if you get weblate.E019 CELERYD_OPTS="--beat:celery --queues:celery=celery CELERYD_LOG_LEVEL="INFO" # Internal Weblate variable to indicate we're running inside Celery CELERY_WORKER_RUNNING="1" Additional configuration to rotate Celery logs using logrotate to be placed as /etc/logrotate

CELERY_BROKER_URL = "memory://" CELERY_TASK_EAGER_PROPAGATES = True You should also start the Celery worker to process the tasks and start scheduled tasks, this can be done directly on the command line (which this line if you don't use an app CELERY_APP="weblate.utils" # Extra command-line arguments to the worker, # increase concurency if you get weblate.E019 CELERYD_OPTS="--beat:celery --queues:celery=celery CELERYD_LOG_LEVEL="INFO" # Internal Weblate variable to indicate we're running inside Celery CELERY_WORKER_RUNNING="1" Additional configuration to rotate Celery logs using logrotate to be placed as /etc/logrotate

CELERY_BROKER_URL = "memory://" CELERY_TASK_EAGER_PROPAGATES = True You should also start the Celery worker to process the tasks and start scheduled tasks, this can be done directly on the command line (which this line if you don't use an app CELERY_APP="weblate.utils" # Extra command-line arguments to the worker, # increase concurency if you get weblate.E019 CELERYD_OPTS="--beat:celery --queues:celery=celery CELERYD_LOG_LEVEL="INFO" # Internal Weblate variable to indicate we're running inside Celery CELERY_WORKER_RUNNING="1" Additional configuration to rotate Celery logs using logrotate to be placed as /etc/logrotate

CELERY_BROKER_URL = "memory://" CELERY_TASK_EAGER_PROPAGATES = True You should also start the Celery worker to process the tasks and start scheduled tasks, this can be done directly on the command line (which this line if you don't use an app CELERY_APP="weblate.utils" # Extra command-line arguments to the worker, # increase concurency if you get weblate.E019 CELERYD_OPTS="--beat:celery --queues:celery=celery CELERYD_LOG_LEVEL="INFO" # Internal Weblate variable to indicate we're running inside Celery CELERY_WORKER_RUNNING="1" Additional configuration to rotate Celery logs using logrotate to be placed as /etc/logrotate

CELERY_BROKER_URL = "memory://" CELERY_TASK_EAGER_PROPAGATES = True You should also start the Celery worker to process the tasks and start scheduled tasks, this can be done directly on the command line (which this line if you don't use an app CELERY_APP="weblate.utils" # Extra command-line arguments to the worker, # increase concurency if you get weblate.E019 CELERYD_OPTS="--beat:celery --queues:celery=celery CELERYD_LOG_LEVEL="INFO" # Internal Weblate variable to indicate we're running inside Celery CELERY_WORKER_RUNNING="1" Additional configuration to rotate Celery logs using logrotate to be placed as /etc/logrotate