Get the sources


git clone


git clone ssh://<FAS user>


The dependencies of mirrormanager2 are listed in the file requirements.txt at the top level of the sources.


if you work in a virtualenv the installation of python-fedora might fail the first time you try, just try to run the command twice, the second time it should work.

Run MirrorManager for development

Copy the configuration file:

cp utility/mirrormanager2.cfg.sample mirrormanager2.cfg

Adjust the configuration file (secret key, database URL, admin group...) See configuration for more detailed information about the configuration.

Create the database scheme:


Run the server:


You should be able to access the server at http://localhost:5000

Every time you save a file, the project will be automatically restarted so you can see your change immediatly.

Coding standards

We are trying to make the code PEP8-compliant. There is a pep8 tool that can automatically check your source.

We are also inspecting the code using pylint and aim of course for a 10/10 code (but it is an assymptotic goal).


both pep8 and pylint are available in Fedora via yum:

yum install python-pep8 pylint

Send patch

The easiest way to work on mirrormanager2 is to make your own branch in git, make your changes to this branch, commit whenever you want, rebase on master, whenever you need and when you are done, send the patch either by email, via the trac or a pull-request (using git or github).

The workflow would therefore be something like:

git branch <my_shiny_feature>
git checkout <my_shiny_feature>
git commit file1 file2
<more work>
git commit file3 file4
git checkout master
git pull
git checkout <my_shiny_feature>
git rebase master
git format-patch -2

This will create two patch files that you can send by email to submit in the trac.


You can send your patch by email to the mirror-list-discuss mailing-list


  • Login fails in development mode

    The Flask FAS extension requires a secure cookie which ensures that it is always encrypted during client/server exchanges. This makes the authentication cookie less likely to be exposed to cookie theft by eavesdropping.

    You can disable the secure cookie for testing purposes by setting the configuration key FAS_HTTPS_REQUIRED to False.


    Do not use this option in production as it causes major security issues


Previous page

← Deployment

Next page

→ Contributing

This Page