Oleg Komarov f20d4c7e99 Replace gunicorn with uwsgi, use persistent db connections (#90) ... The main goal is to configure persistent db connections, this solves two problems: - improves latency - in combination with a fixed number of uwsgi workers it puts a limit on the number of db connections the website can open, and this makes db usage predictable It appears that django doesn't support persistent db connections with asgi yet: https://github.com/django/django/pull/17914#issuecomment-1986390557 https://github.com/django/django/pull/16881 otherwise we could potentially switch to using a connection pool and continue using asgi. This change also makes it more consistent with the rest of our web infra, which is using the same uwsgi deployment model. Deployment: ``` ./ansible.sh -i environments/production install.yaml --tags=pull,uwsgi ./ansible.sh -i environments/production deploy.yaml ``` Reviewed-on: #90 Reviewed-by: Anna Sirota <railla@noreply.localhost>		2024-04-25 15:11:07 +02:00
..
uwsgi.ini	Replace gunicorn with uwsgi, use persistent db connections (#90)	2024-04-25 15:11:07 +02:00
uwsgi.service	Replace gunicorn with uwsgi, use persistent db connections (#90)	2024-04-25 15:11:07 +02:00