summaryrefslogtreecommitdiffstats
path: root/roles/pagure/frontend
Commit message (Collapse)AuthorAgeFilesLines
...
* Let's use the proper configuration key to send email...Pierre-Yves Chibon2016-01-301-1/+1
|
* Prevent a project from being createdPierre-Yves Chibon2016-01-291-1/+1
|
* Pagure should be able to send emailPierre-Yves Chibon2016-01-281-0/+2
|
* Remove action: in all roles.Kevin Fenzi2016-01-061-8/+8
|
* Blacklist projects as project name on pagure, it's an existing URLPierre-Yves Chibon2015-12-071-1/+1
|
* Install and configure the webhook server for pagurePierre-Yves Chibon2015-11-302-0/+4
|
* Add the datagrepper information to pagure configPierre-Yves Chibon2015-11-201-0/+8
|
* Move the folder storing the local clone of remote repo one level upPierre-Yves Chibon2015-11-132-2/+2
| | | | | This fixes ``gitolite trigger POST_COMPILE`` that barfed on this otherwise, but I am not sure why.
* Make pagure.io be before pagure.org so that we always server that SSL cert ↵Pierre-Yves Chibon2015-08-141-21/+24
| | | | by default
* Fix the GIT_URL for the new pagure versionPierre-Yves Chibon2015-08-051-2/+2
|
* Move pagure.io above pagure.org to server pagure.io SSL ceret by defaultPierre-Yves Chibon2015-08-051-35/+36
|
* Add the trailing slash to fix the links in the new version of pagurePierre-Yves Chibon2015-08-051-2/+2
|
* docs in stg now has its own certificatePierre-Yves Chibon2015-08-051-1/+1
|
* Create the remotes folder for the remote PRPierre-Yves Chibon2015-07-312-0/+4
|
* Make a pagure.org -> pagure.io redirectPatrick Uiterwijk2015-07-291-0/+22
|
* Separate Pagure main and Pagure docsPatrick Uiterwijk2015-07-231-1/+2
| | | | | | | | | | | | | | | | RCA of issue sent on IRC: It's a very interresting edge case and related to my previous diag. In short: both the pagure main app and pagure docs app were using the same process pool (WSGIProcessDaemon). As soon as they would both be loaded in the same thread, they would both load the FFI (C wrapper) code, and only the latest process to load it would still have valid type references, the other would start sending wrong references, which causes it to error out (correctly), because it doesn't know the types it got. So basically, the fix I just applied is put pagure docs into its own WSGI daemon process, that keeps them nicely separated. the reason that this didn't hit in staging and why it also worked *sometimes* in production is that it would only crash if: 1. both pagure main app and docs app were loaded in the thread that's used for the current request 2. pagure docs app was loaded last in the current thread, overriding the types for pagure main app, and 3. we have 4 processes with 4 threads each, so each request gets into one of 16 threads, making the staging not likely to hit the previous two conditions, but prod has so many requests it's likely to hit 1 and 2
* Works better w/o typoPierre-Yves Chibon2015-07-231-1/+1
|
* Adjust the apache configuration of docs.pagure.org to be ssl onlyPierre-Yves Chibon2015-07-231-0/+22
|
* Install the ssl certs for docs.pagure.orgPierre-Yves Chibon2015-07-231-0/+3
|
* Adjust pagure config to work.Kevin Fenzi2015-07-231-4/+1
|
* Do not install file that are not presentPierre-Yves Chibon2015-07-201-13/+0
|
* Place all the apache configuration in 0_pagure.conf and drop pagure.confPierre-Yves Chibon2015-07-202-70/+87
|
* Another attempt to fix indentationPierre-Yves Chibon2015-07-201-8/+10
|
* Drop location and fix indentationPierre-Yves Chibon2015-07-201-17/+2
|
* And more adjustmentsPierre-Yves Chibon2015-07-202-16/+4
|
* More adjustements to the apache configuration filePierre-Yves Chibon2015-07-201-14/+19
|
* Move the 0_pagure.conf apache configuration file from a file to a templatePierre-Yves Chibon2015-07-202-3/+7
|
* Adjust the apache configuration for the docs serverPierre-Yves Chibon2015-07-202-9/+15
|
* Fix typo and domain namePierre-Yves Chibon2015-07-201-3/+2
|
* Oups, forgot the filePierre-Yves Chibon2015-07-201-0/+22
|
* Start working on the split of the doc server to a different wsgi appPierre-Yves Chibon2015-07-203-2/+37
|
* Adjust the EV server URL for pagure prodPierre-Yves Chibon2015-06-221-1/+1
|
* Make sure stunnel is correctly workingPierre-Yves Chibon2015-06-191-0/+1
|
* Fix the stunnel configuration and adjust the EV endpointPierre-Yves Chibon2015-06-191-1/+1
|
* Let's not forget to install stunnelPierre-Yves Chibon2015-06-181-0/+1
|
* Start working on stunnel for pagurePierre-Yves Chibon2015-06-183-0/+56
|
* Back to 8080 for pagure-stgPierre-Yves Chibon2015-06-181-1/+1
|
* Move the eventsource port to 9939Pierre-Yves Chibon2015-06-181-1/+1
|
* Adjust the eventsource server urlPierre-Yves Chibon2015-06-181-1/+5
|
* Adjust the pagure playbook for 0.2 with the eventsource serverPierre-Yves Chibon2015-06-182-0/+10
|
* Expand the list of blacklisted projectsPierre-Yves Chibon2015-06-161-1/+3
|
* Ensure all the services are up and running at the end of the playbookPierre-Yves Chibon2015-06-161-10/+15
|
* Let's allow pring statements for now in pagurePierre-Yves Chibon2015-06-141-1/+1
|
* Pass on the Authorization headerPierre-Yves Chibon2015-06-111-0/+1
|
* Add index for the releases dirPierre-Yves Chibon2015-06-051-0/+3
|
* Allow everyone on /releasesPierre-Yves Chibon2015-06-051-0/+14
|
* Add the missing UPLOAD_FOLDERPierre-Yves Chibon2015-06-051-0/+1
|
* Set the UPLOAD_FOLDER_PATHPierre-Yves Chibon2015-06-051-0/+3
|
* Create the alias for /releasesPierre-Yves Chibon2015-06-051-0/+1
|
* Create the /var/www/releases for pagurePierre-Yves Chibon2015-06-051-0/+8
|