pagure is a light-weight git-centered forge based on pygit2.
Python JavaScript HTML CSS Shell Ruby
Latest commit 159ae2f Feb 24, 2017 @pypingou Release 2.13.2
Failed to load latest commit information.
alembic Fix typo in the alembic migration Feb 15, 2017
ansible Drop the FORK_FOLDER configuration key and document it as deprecated Dec 9, 2016
doc Release 2.13.2 Feb 24, 2017
ev-server Handle namespaced projects in SSE server Nov 16, 2016
fedmsg.d Add the config file to initialize the consumer Jul 26, 2016
files Release 2.13.2 Feb 24, 2017
milters Fix the milter to get it working Apr 25, 2016
pagure-ci Only close the DB session at the end Nov 5, 2016
pagure-loadjson Be honest about which data type loadjson supports atm Feb 15, 2017
pagure-logcom Rename the LOG variable to _log, it's a private variable to that module Dec 22, 2016
pagure Release 2.13.2 Feb 24, 2017
tests Add tests for 'open changed file' icon in PR diffs Feb 23, 2017
webhook-server Fix the web-hook server Feb 2, 2017
.gitignore Update the .gitignore file to ignore files generated when ran on jenkins Feb 2, 2017
.pylintrc pylintrc: be more specific about generated-members Nov 16, 2016
LICENSE Add the GPLv2 LICENSE file Sep 2, 2014 Ship pagure-loadjson in the tarball and install it in the spec file Feb 15, 2017
README.rst Update README.rst Nov 14, 2016
UPGRADING.rst Release 2.13 Feb 21, 2017
Vagrantfile.example Create a Vagrantfile and Ansible role for Pagure development Oct 17, 2016 Figure a way to populate the ACL table from the configuration file by… May 22, 2015 Added realname and description data for groups in the dev data generator Aug 29, 2016
nosetests Added commit comparison view Jun 19, 2016
pagure_logo.svg update the logo Mar 15, 2016
requirements-ci.txt Re-structure how are requirements are listed Feb 7, 2017
requirements-ev.txt Re-structure how are requirements are listed Feb 7, 2017
requirements-fedora.txt Add missing requirements for Fedora install Jan 20, 2017
requirements-optional.txt Re-structure how are requirements are listed Feb 7, 2017
requirements-webhook.txt Re-structure how are requirements are listed Feb 7, 2017
requirements.txt Re-structure how are requirements are listed Feb 7, 2017 No longer check the return code, set -e takes care of it Feb 21, 2017 Fix typo in the help string and remove un-needed import Jan 9, 2017 Fix typo in the help string and remove un-needed import Jan 9, 2017 Improve the unit-tests around pagure-ci hook Feb 20, 2017 Drop the moskha.consumer that is no longer used by pagure-ci Dec 16, 2016
tests_requirements.txt No space between name and version Jul 17, 2015



Author:Pierre-Yves Chibon <>

Pagure is a git-centered forge, python based using pygit2.

With pagure you can host your project with its documentation, let your users report issues or request enhancements using the ticketing system and build your community of contributors by allowing them to fork your projects and contribute to it via the now-popular pull-request mechanism.


See it at work:

Playground version:

Get it running

There are several options when it comes to a development environment. Vagrant will provide you with a virtual machine which you can develop on, or you can install it directly on your host machine.


For a more thorough introduction to Vagrant, see

An example Vagrantfile is provided as Vagrantfile.example. To use it, just copy it and install Vagrant:

$ cp Vagrantfile.example Vagrantfile
$ sudo dnf install ansible libvirt vagrant-libvirt vagrant-sshfs vagrant-hostmanager
$ vagrant up

The default Vagrantfile forwards ports from the host to the guest, so you can interact with the application as if it were running on your host machine.


vagrant-hostmanager will automatically maintain /etc/hosts for you so you can access the development environment from the host using its hostname, which by default is You can choose not to use this functionality by simply not installing the vagrant-hostmanager plugin, but if you want Pagure to provide valid URLs in the UI for git repositories, you will need to adjust Pagure's configuration found in ~/pagure.cfg on the guest.


  • Install the needed system libraries:

    sudo dnf install git python2-virtualenv libgit2-devel \
                     libjpeg-devel gcc libffi-devel redhat-rpm-config


    Do note the version of libgit2 that you install, for example in libgit2-0.23.4-1 you need to keep in mind the 0.23


    On Fedora 23 and earlier or on RHEL and derivative (CentOS, Scientific Linux) the package python2-virtualenv is named python-virtualenv

  • Retrieve the sources:

    git clone
    cd pagure
  • Install dependencies

    • create the virtualenv:

      virtualenv pagure_env
      source ./pagure_env/bin/activate
    • Install the correct version of pygit2:

      pip install pygit2==<version of libgit2 found>.*

      So in our example:

      pip install pygit2==0.23.*
    • Install the rest of the dependencies:

      pip install -r requirements.txt
  • Create the folder that will receive the projects, forks, docs, requests and tickets' git repo:

    mkdir {repos,docs,forks,tickets,requests}
  • Create the inital database scheme:

  • Run it:

  • To get some profiling information you can also run it as:

    ./ --profile

This will launch the application at

  • To run unit-tests on pagure

    • Install the dependencies:

      pip install -r tests_requirements.txt
    • Run it: