From caef74e95541b2d6900e609778d9deb50fc5c551 Mon Sep 17 00:00:00 2001
From: Gregor Kleen <kleen@cip.ifi.lmu.de>
Date: Thu, 9 May 2019 16:17:43 +0200
Subject: [PATCH] Make maximum-content-length easier configurable at runtime

See #357
---
 config/settings.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/config/settings.yml b/config/settings.yml
index aba8f93c3..592b09ca1 100644
--- a/config/settings.yml
+++ b/config/settings.yml
@@ -29,7 +29,7 @@ notification-expiration: 259201
 session-timeout: 7200
 jwt-expiration: 604800
 jwt-encoding: HS256
-maximum-content-length: 134217728
+maximum-content-length: "_env:MAX_UPLOAD_SIZE:134217728"
 health-check-interval: "_env:HEALTHCHECK_INTERVAL:600" # or WATCHDOG_USEC/2, whichever is smaller
 health-check-http: "_env:HEALTHCHECK_HTTP:true"
 health-check-delay-notify: "_env:HEALTHCHECK_DELAY_NOTIFY:true"