Merge pull request #308 from OperationCode/update-uwsgi-settings

Update the uwsgi settings with better production features

Author: Aaron Suarez

Dockerfile

@@ -13,7 +13,7 @@ COPY pyproject.toml poetry.lock ./
 RUN mkdir /static
 
 RUN apt-get update \
-    && apt-get install -y libpq-dev gcc \
+    && apt-get install -y libpq-dev gcc libpcre3 libpcre3-dev \
     && rm -rf /var/lib/apt/lists/* \
     && pip install --upgrade pip \
     && pip install poetry \

app.ini

@@ -1,5 +1,13 @@
 ; app.ini
+
+; NOTE: The configuration in this file came from the following
+; sources. These should answer the "why" of the decision for
+; each of the configuration options:
+; - https://medium.com/bitcraft/docker-composing-a-python-3-flask-app-line-by-line-93b721105777
+; - https://www.techatbloomberg.com/blog/configuring-uwsgi-production-deployment/
+
 [uwsgi]
+strict = true
 protocol = uwsgi
 ; This is the name of our Python file
 ; minus the file extension
@@ -15,3 +23,11 @@ processes = 2
 http = 0.0.0.0:5000
 vacuum = true
 die-on-term = true
+single-interpreter = true
+need-app = true
+
+; The logs in production are really hard to sift through because
+; the /healthz route is called so often. We don't need to log
+; every time the cluster does a healthcheck.
+route = ^/healthz donotlog:
+route = ^/metrics donotlog: