pagure is a light-weight git-centered forge based on pygit2.
Python HTML JavaScript CSS Shell Ruby
pypingou Release 4.0.1
Signed-off-by: Pierre-Yves Chibon <>
Latest commit 42ea2a1 Apr 26, 2018
Failed to load latest commit information.
alembic Fix the alembic migration, in postgresql quotes matter Apr 16, 2018
dev Migrate the jenkins job data to new db schema Apr 12, 2018
doc Release 4.0.1 Apr 26, 2018
fedmsg.d Add the config file to initialize the consumer Jul 26, 2016
files Release 4.0.1 Apr 26, 2018
pagure-ev Re-architure pagure Jan 3, 2018
pagure-milters Re-architure pagure Jan 3, 2018
pagure Release 4.0.1 Apr 26, 2018
tests Fix browsing projects in a namespace when logged in. Apr 26, 2018
utils Fix symlink Mar 23, 2018
.cico.pipeline Do not fail if the post call to pagure times out Apr 13, 2018
.flake8 pep8 fixes and add a .flake8 configuration file Apr 10, 2017
.gitignore Make the docker test environment easier to use. Mar 15, 2018
.pylintrc pylintrc: be more specific about generated-members Nov 16, 2016
LICENSE Add the GPLv2 LICENSE file Sep 2, 2014 Clean up the file since we dropped some folders Apr 16, 2018
README.rst document redis server start Mar 19, 2018
UPGRADING.rst Release 3.13.1 Dec 19, 2017 Re-architure pagure Jan 3, 2018 Re-architure pagure Jan 3, 2018
nosetests Add performance totals plugin Mar 21, 2017
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 fedora req: fix package name for bcrypt Dec 4, 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 Enable usage of flask-session extension Apr 25, 2018 debug the environment in the ci_tests script Apr 12, 2018 Fix typo in the help string and remove un-needed import Jan 9, 2017 Re-architure pagure Jan 3, 2018 Add performance totals plugin Mar 21, 2017 Drop the --autoreload argument Jun 1, 2017 Allow customizing the writing of gitolite's configuration file Jun 28, 2017
tests_requirements.txt Fix the flakiness of some tests Mar 20, 2018



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:

If you have any questions or just would like to discuss about pagure, feel free to drop by on IRC in the channel #pagure of the freenode server

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 dev/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.

Docker Compose

Create the folder that will receive the projects, forks, docs, requests and tickets' git repo:

mkdir -p lcl/{repos,remotes,attachments,releases}

A docker compose environment is available to run pagure. First use the following command to build the containers.

$ docker-compose -f dev/docker-compose.yml build

Once all the containers are built, run the following command to start the containers.

$ docker-compose -f dev/docker-compose.yml up -d

Once all the containers have started, you can access pagure on http://localhost:5000

To stop the containers, run the following

$ docker-compose -f dev/docker-compose.yml stop

More information about docker-compose cli see

Running the unit-tests

To run the unit-tests, there is container available with all the dependencies needed.

Use the following command to run the tests

$ ./dev/

This command will build a fedora based container and execute the test suite.

If you wish to execute the test suite on a centos based container run the following command

$ ./dev/ --centos

When the test container image has been built you can skip the building step to save time and run directly the test suite.

$ ./dev/ --skip-build
$ ./dev/ --centos --skip-build

You can also run a single test case

$ ./dev/ tests/

Or a single test

$ ./dev/ tests/

You can also get run-tests-docker help

$ ./dev/ --help


  • Install the needed system libraries:

    sudo dnf install git python2-virtualenv libgit2-devel redis \
                     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 -p lcl/{repos,remotes,attachments,releases}
  • Copy and edit the alembic.ini file (especially the script_location key):

    cp files/alembic.ini .
    vim alembic.ini
  • Set the script_location to alembic, ie: the folder where the revisions are stored, relative to the location of the alembic.ini file.

  • Create the inital database scheme:

    python --initial alembic.ini
  • Enable and start redis server:

    systemctl enable redis
    systemctl start redis
  • Start a worker, in one terminal:

  • Run the application, in another terminal:

  • 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:



      While testing for worker tasks, pagure uses celery in /usr/bin/ Celery then looks for eventlet (which we use for testing only) at system level and not in virtualenv. You will need to install eventlet outside of your virtualenv if you are using one.