From 2711f90e74d858bdd7497912aae10208afad02f2 Mon Sep 17 00:00:00 2001
From: Neal Gompa <ngompa@opensuse.org>
Date: Nov 16 2020 23:32:17 +0000
Subject: pagure: Allow git push via HTTPS


If users have an API token to allowing committing via HTTPS, we
should allow it to work. Additionally, ensure nginx doesn't truncate
git push requests proxied through.

---

diff --git a/pillar/role/pagure.sls b/pillar/role/pagure.sls
index 73ea875..56f7391 100644
--- a/pillar/role/pagure.sls
+++ b/pillar/role/pagure.sls
@@ -39,6 +39,7 @@ nginx:
                     - 80
                     - default_server
                 - location @pagure:
+                    - client_max_body_size: 0
                     - proxy_set_header: Host $http_host
                     - proxy_set_header: X-Real-IP $remote_addr
                     - proxy_set_header: X-Forwarded-For $proxy_add_x_forwarded_for
diff --git a/salt/profile/pagure/files/pagure.cfg b/salt/profile/pagure/files/pagure.cfg
index 2ea0afc..92d6e17 100644
--- a/salt/profile/pagure/files/pagure.cfg
+++ b/salt/profile/pagure/files/pagure.cfg
@@ -63,6 +63,9 @@ SALT_EMAIL = '{{ pillar['profile']['pagure']['salt_email'] }}'
 ## anymore as a selection in the PR dropdown menus
 DISABLE_REMOTE_PR = False
 
+### Allow HTTP(S) pushes with local/token auth
+ALLOW_HTTP_PUSH = True
+
 ### The URL at which the project is available.
 APP_URL = 'https://code.opensuse.org/'
 ### The URL at which the documentation of projects will be available