1546503 - Ability to control gunicorn and celery workers in local dev

Status: RESOLVED FIXED

(developer.mozilla.org Graveyard :: General, enhancement, P5)

Description

[Peter Bengtsson [:peterbe]]

As of today, when you run docker-compose up it starts 4 celery workers and 4 gunicorn workers. That's pretty hefty and resource intensive.

You could follow the development instructions to "Customizing the Docker environment" by writing your own docker-compose.dev.yml to your own liking. But that's not without risk when the default docker-compose.yml changes. Being able to control this once from your personal .env would be nicer.

Comment 1

[Peter Bengtsson [:peterbe]]

One option is to control gunicorn with GUNICORN_CMD_ARGS but it requires that you want to control all the other things. Not just the number of workers. Also, that solution is unique to gunicorn.

Comment 2

[GitHub Bugzilla PR Linker]

Attachment: Link to GitHub pull-request: https://github.com/mozilla/kuma/pull/5368

Comment 3

[Peter Bengtsson [:peterbe]]

Merged in master and doesn't depend on production deployment.