No Description

Zbigniew Jędrzejewski-Szmek 3a89a5af4f srcfpo theme: left-align the lines in description 10 months ago
alembic 1815160207 Make the token_id column of the commit_flags table nullable 1 year ago
dev 292391cdd1 Add missing test dependencies for CI containers 11 months ago
doc 0e0d3ff0ca Change fas link from admin.fp.o to accounts.fp.o 1 year ago
fedmsg.d 73d1200552 Project wide black fixes, including tests, docs and all 3 years ago
files f2574fb32d Sync runtime dependencies from requirements.txt to the spec 11 months ago
pagure 3a89a5af4f srcfpo theme: left-align the lines in description 10 months ago
pagure-ev 73d1200552 Project wide black fixes, including tests, docs and all 3 years ago
pagure-milters d773bb2be5 Make the milter discard the messages when it's done 1 year ago
tests 7591a37365 tests: Use the correct test case data for Markdown on Python 3 10 months ago
utils 85f82260ee Drop remaining nose files and requirements 1 year ago
.cico.pipeline 122eea5215 Escape $ to fix Jenkins interpolation warning (#5178) 1 year ago
.flake8 a6b52c1146 Adjust pagure's source code for the newer flake8 2 years ago
.gitignore 437bdfa6bf Adding to .gitignore file 2 years ago
.pylintrc 254a80ed21 pylintrc: be more specific about generated-members 5 years ago
LICENSE 96994225ac Add the GPLv2 LICENSE file 8 years ago f8d23a53ad Clean up the file since we dropped some folders 4 years ago
README.rst 37589c32d3 Update README 1 year ago
UPGRADING.rst 967d458565 Update fedmsg homepage 1 year ago 73d1200552 Project wide black fixes, including tests, docs and all 3 years ago 75f7c960ea Add orphaning reason 2 years ago
pagure_logo.svg 43167e1e09 update the logo 6 years ago
pyproject.toml d5a073b055 Let's see if pyproject will work in jenkins 3 years ago
requirements-ci.txt 33bdcafbcf trollius → trololio 4 years ago
requirements-ev.txt 33bdcafbcf trollius → trololio 4 years ago
requirements-fedora.txt da0c1b6eef Add a dependency on flask-oidc for testing 1 year ago
requirements-optional.txt 71c8894fd4 Re-structure how are requirements are listed 5 years ago
requirements-testing.txt b0fb05304c Port pagure to the latest version of python black 1 year ago
requirements-webhook.txt 33bdcafbcf trollius → trololio 4 years ago
requirements.txt 677a9ab2a3 Drop Python 2 support in spec file and requirements 11 months ago 1d70c7f1fd Finish replacing CentOS 7 with CentOS Stream 8 in CI 11 months ago 73d1200552 Project wide black fixes, including tests, docs and all 3 years ago 4479b18d1e Add PAGURE_PLUGINS_CONFIG setting in pagure configuration file. 2 years ago 56cfd67754 Reorder celery arguments (and s/info/INFO/) 11 months ago 677a9ab2a3 Drop Python 2 support in spec file and requirements 11 months ago
tox.ini 677a9ab2a3 Drop Python 2 support in spec file and requirements 11 months ago



: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

About its name

The name Pagure is taken from the French word 'pagure'. Pagure in French is used as the
common name for the crustaceans from the `Paguroidea `_
superfamily, which is basically the family of the Hermit crabs.

Originating from French it is pronounced with a strong 'g' as you can hear
on `this recording `_.

Get it running

There are several options when it comes to a development environment.
They are: Docker Compose, Vagrant, and manual. Choose an option below.

Docker Compose
Docker Compose will provide you with a container which you can develop on.
Install it `with these instructions `_.

For more information about docker-compose cli, see:

To build and run the containers, use the following command::

$ ./dev/

Once all the containers have started, you can access pagure on http://localhost:5000.
To stop the containers, press Ctrl+C.

Once the containers are up and running, run this command to populate the
container with test data and create a new account ::

$ docker-compose -f dev/docker-compose.yml exec web python3 --all

You can then login with any of the created users, by example:

- username: pingou
- password: testing123


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. Instructions for Fedora::

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

On Ubuntu, install Vagrant directly `from the website `_
then run these commands instead::

$ cp dev/Vagrantfile.example Vagrantfile
$ sudo add-apt-repository ppa:ansible/ansible
$ sudo apt update
$ sudo apt install ansible libvirt0 openssh-server qemu libvirt-bin ebtables dnsmasq libxslt-dev libxml2-dev libvirt-dev zlib1g-dev ruby-dev
$ vagrant plugin install vagrant-libvirt vagrant-sshfs vagrant-hostmanager

If you get this error ``Block in synced_folders: Internal error. Invalid: sshfs``,
when you run ``vagrant up`` , you need to install vagrant sshfs plugin, which can be done by::

$ vagrant plugin install vagrant--sshfs

and then::

$ 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.

.. note::
``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.

When the vagrant VM is up and running, connect to it with::

$ vagrant ssh

This will log you into the VM as the user ``vagrant`` which has a couple of aliases

$ pstart # Starts pagure, the workers and other tasks
$ pstop # Stops all those tasks again
$ pstatus # Shows pagure status

The Vagrant pagure doesn't have its own log file, use ``journalctl -f`` to
show the pagure output. The verbosity can be configured in the pagure config file
with the ``LOGGING`` parameter.

Running the unit-tests

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

First you will need to have podman installed on your workstation. ::

$ sudo dnf install podman

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-container` help ::

$ ./dev/ --help


* Install the needed system libraries::

sudo dnf install git python3 python3-devel libgit2-devel redis \
libjpeg-devel gcc libffi-devel redhat-rpm-config

.. note:: Do note the version of libgit2 that you install, for example
in ``libgit2-0.26.8-1`` you need to keep in mind the ``0.26``

.. note:: On RHEL and derivative (CentOS, Scientific Linux) there is no
`python3` package. Just `python36` or `python34` available in
EPEL 7 (EPEL 6 only has `python34`). Choose the one you prefer
(3.6 is newer and generally a better choice).

* Retrieve the sources::

git clone
cd pagure

* Install dependencies

* create the virtual environment (use `python3.X` explicitly on EPEL)::

python3 -m venv pagure_env
source ./pagure_env/bin/activate

* Install the correct version of pygit2::

pip install pygit2==.*

So in our example::

pip install pygit2==0.26.*

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

sudo systemctl enable redis
sudo 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 requirements-testing.txt

* Run it::

pytest tests/

.. note:: 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 virtual environment. You will need to
install eventlet outside of your virtual environment if you are
using one.

.. note:: This will also work in vagrant.