EDIT ipeer web proxy fastcgi_read_timeout config

The web proxy was timing out in 1 minute and some iPeer requests needed
longer to process, so I've added a values config web.timeout that lets
you configure fastcgi_read_timeout to a longer time.

I suspect our kubernetes ingress is already on a longer timeout, as I
didn't need to explicitly configure proxy-read-timeout and such for
ingress for the longer timeout to work.

ipeer/Chart.yaml

@@ -15,7 +15,7 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 0.1.8
+version: 0.1.9
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to

ipeer/templates/nginx-configmap.yaml

@@ -34,6 +34,7 @@ data:
         location ~ \.php$ {
           include fastcgi_params;
           fastcgi_index index.php;
+          fastcgi_read_timeout {{ .Values.web.timeout }};
           fastcgi_param REQUEST_METHOD $request_method;
           fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
           fastcgi_pass 127.0.0.1:9000;

ipeer/values.yaml

@@ -17,7 +17,9 @@ web:
   image:
     repository: nginx
     pullPolicy: IfNotPresent
-    tag: "1.19-alpine"
+    tag: "1.24-alpine"
+  # set request timeout in seconds, some results need more time to calculate
+  timeout: "300"
 
 worker:
   enabled: false