gunicorn settings not tunable and confusing

The daisy-app as deployed by juju uses the gunicorn subordinate charm to provide gunicorn/wsgi app running.

gunicorn has tunables, such as wsgi_workers that update the config in /etc/init/gunicorn.service - and indeed make you think you are updating the deployment to scale it out on a beefier instance for instance.

That is *not* the case however.

The charm hard codes /etc/systemd/gunicorn.service with --workers=3 (in configure_gunicorn). This makes the service both untunable in production - and is totally confusing and time wasting to Ops staff!