Skip to content
Feedparser-based feed aggregation django app
Python HTML CSS CoffeeScript
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
feedjack README: add deprecation notice Aug 2, 2016
.gitignore README: use rst instead of markdown Apr 30, 2015
CHANGES CHANGES: add note on the list not being maintained anymore Apr 29, 2015
LICENSE Initial svn import Jul 29, 2006 README: use rst instead of markdown Apr 30, 2015
README README: use rst instead of markdown Apr 30, 2015
README.rst README: add deprecation notice Aug 2, 2016
requirements.txt README: use rst instead of markdown Apr 30, 2015



Deprecation notice: this fork of the project is pretty much abandoned and haven't seen updates in a while, please check out other github forks (e.g. allo-/feedjack) for more up-to-date and feature-complete versions.

Feedjack is a feed aggregator, allowing to aggregate multiple rss/atom feeds into multiple "sites", accessible as regular web pages, somewhat like "planet" aggregator does, but better.

It is intended to be useful as a multisite feed aggregator (planet, e.g. "planet python"), as well as a personal feed reader app with web interface. It's also a Django app, which can be integrated into larger Django projects.

This project is a fork of the original Feedjack project by Gustavo Picón, which seem to be abandoned for a while now. See CHANGES file for more details on what happened here over time.


Python module (Django app)

This feedjack fork is a regular package for Python 2.7 (not 3.X).

Best way to install it (from PyPI) would be to use pip:

% pip install Feedjack

If you don't have it, use:

% easy_install pip
% pip install Feedjack

Alternatively (see also and pip install guide):

% curl | python
% pip install Feedjack

Current-git version can be installed like this:

% pip install 'git+'

All of these will automatically fetch and install 'feedjack' Django app to a configured python site-path, along with all the required dependencies.

Another way of installing from a git chechout would be running python install in the dir.

Note that to install stuff in system-wide PATH and site-packages, elevated privileges are often required. Use "install --user", ~/.pydistutils.cfg or virtualenv to do unprivileged installs into custom paths.

Django project

If you are not familiar with Django framework and how Django apps are deployed, please see this short tutorial, which contains all the steps necessary to initialize "django project" directory, also explaining what's in there:

Django project - at it's minimum - is just a few configuration files, specifying which database to use, and which "apps" should handle which URLs.

Feedjack can only be deployed as an "app" in such project, so it either has to be created, or app can be enabled in any existing one.

Enabling app in a Django project

  • First of all, 'feedjack' app must be enabled in under INSTALLED_APPS.

  • Running ./ migrate ("migrate" command, supersedes "syncdb" in Django-1.7+) from the command line should then populate database (whichever is configured in the same file) with feedjack-specific schema.

  • Feedjack "static files" directory should be setup to be reachable under configured STATIC_URL (under "STATIC_URL/feedjack/", to be precise).

    This can be done automatically by using django.contrib.staticfiles app, that will copy/link static files with ./ collectstatic command.

    It can also be done manually. For instance, if your STATIC_URL resolves to "/var/www/htdocs", and Feedjack was installed to "/usr/lib/python2.7/site-packages/feedjack", symlinking dir from there should probably do the trick:

    % ln -s /usr/lib/python2.7/site-packages/feedjack/static/feedjack /var/www/htdocs/
  • Be sure to enable/add/uncomment/check "django.contrib.admin" app (Django admin interface) as well, since it's the most convenient and supported way to configure and control feedjack.

    "migrate" operation (same as after enabling feedjack itself) might be necessary after that.

    Other ways to configure and control feedjack app after installation are:

    • Command-line tools.

      These are accessible via (or "./" wrapper) - see --help output for reference on all the supported commands there.

      Some (e.g. "feedjack_update") can also be installed as python console_scripts entry points.

    • Manipulate models from the python code or ./ shell directly, which might be desirable for some kind of migration or automated configuration.

  • Add an entry for feedjack.urls in your Django "" file, so it'd look like this (with admin interface also enabled on "/admin/"):

    urlpatterns = patterns( '',
      (r'^admin/', include('django.contrib.admin.urls')),
      (r'', include('feedjack.urls')) )

    (of course, less trivial Django configurations should probably have way more entries there)

After all that, it might be worth checking out "/admin" interface (if django.contrib.admin app was enabled) to create a feedjack site, otherwise sample default site will be created upon first request.

Be sure to check out deployment section of Django docs and a checklist there before making project accessible from the internet:

See also "Configuration" section below.


  • Python 2.7 (not 3.X)
  • Django 1.8+
  • feedparser 4.1+
  • (optional, recommended) pytz - required by Django in some cases, facilitates correct handling/interpretation of timezones.
  • (optional) lxml - used for html mangling in some themes (fern, plain) processing of more free-form timestamps on feeds, if feedparser can't handle these for whatever reason.
  • (optional, only for updating from older Feedjack/Django versions) South

Updating from older versions

The only non-backwards-compatible changes should be in the database schema, thus requiring migration, but it's much easier (automatic even) than it sounds.

Feedjack didn't have any automatic db migration features in the past, then used South module (in this fork), and now uses stock Django database migration features (which only work with Django-1.7+).

  • To upgrade older installations where there were no migrations in use at all, install and enable South app, backup "feedjack/migrations" (which now contains Django-native migration info), then rename "feedjack/migrations.south" dir to "feedjack/migrations".

    There is no automated way to determine schema version in current database, so use South's ./ migrate --list command to list migrations, find the one that matches current db state and run e.g. ./ migrate feedjack 0013 --fake to make South aware of it.

    In case of pre-fork Feedjack versions (0.9.16 and below), this would be very first (0001) schema version.

  • To upgrade from South to Django-1.7+ native migrations, temporarily restore "migrations.south" dir to "migrations", as outlined above, run ./ migrate to make sure all South migrations were applied, then restore Django's "migrations" directory, replace "south" with "django.db.migrations" in INSTALLED_APPS and run ./ migrate again to apply all these.

    See also Upgrading from South section in Django docs on migrations.


The first thing you want to do is to add a Site.

To do this, open Django admin interface and create your first planet. You must use a valid address in the URL field, since it will be used to identify the current planet when there are multiple planets in the same instance and to generate all the links.

Then you should add Subscribers to your first planet. A Subscriber is a relation between a Feed and a Site, so when you add your first Subscriber, you should also add your first Feed by clicking in the “+” button at the right of the Feed combobox.

Feedjack is designed to use Django cache system to store database-intensive data like pages of posts and tagclouds, so it is highly recomended to configure CACHES in django settings (memcached, db, files, etc). Feedjack will try to use cache with "feedjack" alias, falling back to "default" if that one is not defined.

Now that you have everything set up, run ./ feedjack_update (or something like DJANGO_SETTINGS_MODULE=myproject.settings feedjack_update) to retrieve the actual data from the feeds. This script should be setup to be run periodically (to retreive new posts from the feeds), which is usually a task for unix cron daemon.

In case of some missing or inaccessible functionality, feedjack may issue (once per runtime) python warnings, which can (and most likely should) be captured by logging system, so they can be handled by django (e.g. notification mail sent to ADMINS).

To do that, add following code to Django's

import logging


Navigate to http(s) url where Django app is deployed and you should see a page with aggregation of all the stuff from configured feeds, or maybe an empty page if none were configured or fetched.

Updates to feeds (fetching new entries) happen only on running feedjack_update command, which (among others) can be used either as a command-line script (installed by as a cli entry point) or a regular Django management command.

Management commands

Feedjack app adds several Django management commands, full list of which can be found by running e.g. ./ help (or similar thing via

Run each one of these with --help (or -h) option to see full info on the particular command.

  • feedjack_update

    Fetches new items for all active (default) or a specified sites/feeds (see command-line --site and --feed options).

  • feedjack_add_feed

    Adds specified feed, with optional adding of site subscriber, fetching (see also --hidden option to make only future entries show up) and related stuff.

  • feedjack_status

    General command to list all sites/feeds and various information on these.

  • feedjack_purge

    Command to cleanup (purge) feed entries by specified criteria.

    Most common use is probably "by-age" subcommand, allowing to drop way-too-old posts (or newer ones, be sure to check out --dry-run option and lists of posts with --debug - might be useful to do before actual removal).

There might be more command since this README was updated, see ./ help and --help in these for a full list and/or info on each.

Bugs, development, support

All the issues with this fork should probably be reported to respective github project/fork, since code here can be quite different from the original project.

Until 2012, this fork was kept in a fossil repo here.


You can’t perform that action at this time.