From 1560efe9c93b17438ab37d94443832dde3842637 Mon Sep 17 00:00:00 2001 From: Matthew Treinish Date: Fri, 30 Jun 2017 12:15:26 -0400 Subject: [PATCH] Switch local http uwsgi conf to http-socket mode Previously the local uwsgi server mode was using uwsgi in http mode. This was unessecary and actually not recommend by the uwsgi docs [1][2] This is because http mode starts a frontend http process that forwards requests to the workers running the python code. This is done for the largely the same reasons we're using apache as a proxy and is unnecessary. http-socket mode doesn't do this and just exposes the workers as an http interface to the proxy. (in our case apache) [1] http://uwsgi-docs.readthedocs.io/en/latest/HTTP.html#http-sockets [2] http://uwsgi-docs.readthedocs.io/en/latest/ThingsToKnow.html Change-Id: I5671687c8083fa4bdee066c07b083a0f00be532b --- lib/apache | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/apache b/lib/apache index cf438a0794..445241e707 100644 --- a/lib/apache +++ b/lib/apache @@ -301,7 +301,7 @@ function write_local_uwsgi_http_config { rm -rf $file iniset "$file" uwsgi wsgi-file "$wsgi" port=$(get_random_port) - iniset "$file" uwsgi http "127.0.0.1:$port" + iniset "$file" uwsgi http-socket "127.0.0.1:$port" iniset "$file" uwsgi processes $API_WORKERS # This is running standalone iniset "$file" uwsgi master true