Anitya is a release monitoring project.

Its goal is to regularly check if a project has made a new release. Originally developed within Fedora, the project created tickets on the Fedora bugzilla when a new release is available. Now this service has been split into two parts:

• anitya: find and announce new releases
• the new hotness: listens to the fedmsg bus, opens a ticket on bugzilla for packages allowing for it and triggers a scratch-build of the new version

Anitya provides a user-friendly interface to add or edit projects. New releases are announced on fedmsg and notifications can then be sent via FMN (the FedMsg Notifications service).

Anitya is built using python2.x. The following steps all are setup using virtualenv having python2.x.

Note: The project will not work with python3 (yet.)

Here are some preliminary instructions about how to stand up your own instance of anitya. We'll use a virtualenv and a sqlite database and we'll install our dependencies from the Python Package Index (PyPI). None of these are best practices for a production instance, but they will do for development.

First, set up a virtualenv:

$ sudo yum install python-virtualenv
$ virtualenv anitya-env --system-site-packages
$ source anitya-env/bin/activate

Issuing that last command should change your prompt to indicate that you are operating in an active virtualenv.

Next, install your dependencies:

(anitya-env)$ pip install -r requirements.txt

Create the database, by default it will be a sqlite database located at /var/tmp/anitya-dev.sqlite:

(anitya-env)$ python createdb.py

If all goes well, you can start a development instance of the server by running:

(anitya-env)$ python runserver.py

Open your browser and visit http://localhost:5000 to check it out.

You can use dockerfile provided in root of this repository. Build it:

$ cd anitya/
$ docker build --tag=anitya .

And run:

$ docker run --net=host anitya

--net=host will use network stack from your host system. Application will be then available on localhost at http://localhost:5000.

If you inspect the dockerfile you can see that installation method is almost identical to the described in section virtualenv.