#4853 Add nginx configuration variant and split webserver configuration in packaging
Merged by pingou. Opened by ngompa.
ngompa/pagure nginx-config  into  master

Download 4853.patch

This change adds a working nginx configuration for Pagure using
nginx and gunicorn. In addition, to support Pagure deployments
using either configuration, the webserver configuration files
have been split out into their own subpackages.

This is built on top of #4848, as this configuration requires the changes in that code.

9 new commits added

  • Add nginx configuration variant and split webserver configuration in packaging
  • Rename the apache httpd configuration file
  • Drop the proxying to git-http-backend via the apache configuration file
  • Adjust the realm sent back based on the auth configured
  • Add tests for the http-base push
  • Make the tests PagureFlaskApiIssuetests.test_api_assign_issue more robust
  • If pagure is set up for local auth, allow git push via https using it
  • Move the logic checking if the username and password are valid to pagure.lib
  • Add support for git push via http using basic auth relying on API token

9 new commits added

  • Add nginx configuration variant and split webserver configuration in packaging
  • Rename the apache httpd configuration file
  • Drop the proxying to git-http-backend via the apache configuration file
  • Adjust the realm sent back based on the auth configured
  • Add tests for the http-base push
  • Make the tests PagureFlaskApiIssuetests.test_api_assign_issue more robust
  • If pagure is set up for local auth, allow git push via https using it
  • Move the logic checking if the username and password are valid to pagure.lib
  • Add support for git push via http using basic auth relying on API token

9 new commits added

  • Add nginx configuration variant and split webserver configuration in packaging
  • Rename the apache httpd configuration file
  • Drop the proxying to git-http-backend via the apache configuration file
  • Adjust the realm sent back based on the auth configured
  • Add tests for the http-base push
  • Make the tests PagureFlaskApiIssuetests.test_api_assign_issue more robust
  • If pagure is set up for local auth, allow git push via https using it
  • Move the logic checking if the username and password are valid to pagure.lib
  • Add support for git push via http using basic auth relying on API token

9 new commits added

  • Add nginx configuration variant and split webserver configuration in packaging
  • Rename the apache httpd configuration file
  • Drop the proxying to git-http-backend via the apache configuration file
  • Adjust the realm sent back based on the auth configured
  • Add tests for the http-base push
  • Make the tests PagureFlaskApiIssuetests.test_api_assign_issue more robust
  • If pagure is set up for local auth, allow git push via https using it
  • Move the logic checking if the username and password are valid to pagure.lib
  • Add support for git push via http using basic auth relying on API token

9 new commits added

  • Add nginx configuration variant and split webserver configuration in packaging
  • Rename the apache httpd configuration file
  • Drop the proxying to git-http-backend via the apache configuration file
  • Adjust the realm sent back based on the auth configured
  • Add tests for the http-base push
  • Make the tests PagureFlaskApiIssuetests.test_api_assign_issue more robust
  • If pagure is set up for local auth, allow git push via https using it
  • Move the logic checking if the username and password are valid to pagure.lib
  • Add support for git push via http using basic auth relying on API token

rebased onto d1409b1991f1e59949d4fb970d362abd59b275df

rebased onto d0fba4123edcb9143f381d2a23d0ca393fde40aa

This needs a rebase now that #4848 has been merged :)

rebased onto 9392ab393a38920128ee09b0c926dfd16f068e2d

@pingou Done.

Gee this spec file is getting hairy :)

Pull-Request has been merged by pingou

@pingou Yep! I think at some point soon I'm going to have to look at whether we can do anything to simplify it. For now, I think it's fine.

Metadata