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.
This feedjack fork is a regular package for Python 2.7 (not 3.X).
% pip install Feedjack
If you don't have it, use:
% easy_install pip % pip install Feedjack
% curl https://raw.github.com/pypa/pip/master/contrib/get-pip.py | python % pip install Feedjack
Current-git version can be installed like this:
% pip install 'git+https://github.com/mk-fg/feedjack.git#egg=Feedjack'
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 setup.py 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.
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.
Running ./manage.py 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).
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:
Some (e.g. "feedjack_update") can also be installed as python console_scripts entry points.
Manipulate models from the python code or ./manage.py shell directly, which might be desirable for some kind of migration or automated configuration.
Add an entry for feedjack.urls in your Django "urls.py" 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.
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 ./manage.py migrate --list command to list migrations, find the one that matches current db state and run e.g. ./manage.py 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 ./manage.py 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 ./manage.py 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 ./manage.py 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 settings.py:
import logging logging.captureWarnings(True)
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.
|File||Type||Python Version||Uploaded On||Downloads|
|Feedjack-15.03.1.tar.gz||Source||March 29, 2015||304|
|15.03.1||March 29, 2015|
|15.03.0||March 25, 2015|
|15.02.46||Feb. 9, 2015|
|15.02.45||Feb. 9, 2015|
|15.02.44||Feb. 9, 2015|
|15.02.43||Feb. 9, 2015|
|15.02.42||Feb. 8, 2015|
|15.02.30||Feb. 6, 2015|
|15.02.29||Feb. 6, 2015|
|15.02.27||Feb. 4, 2015|
|15.02.25||Feb. 3, 2015|
|15.02.17||Feb. 3, 2015|
|15.02.16||Feb. 3, 2015|
|15.02.15||Feb. 3, 2015|
|0.9.20||March 17, 2014|
|0.9.19||March 17, 2014|
|0.9.18||Jan. 26, 2014|
|0.9.17||Jan. 26, 2014|
|0.9.16.1||Sept. 1, 2011|
|0.9.16||Sept. 9, 2010|
|April 18, 2015, 4:27 p.m.||Feedjack||15.02.27||Release Created|
|April 18, 2015, 4:27 p.m.||Feedjack||0.9.17||Release Created|
|April 18, 2015, 4:27 p.m.||Feedjack||0.9.16.1||Release Created|
|April 18, 2015, 4:27 p.m.||Feedjack||15.02.29||Release Created|
|April 18, 2015, 4:27 p.m.||Feedjack||15.02.15||Release Created|
|April 18, 2015, 4:27 p.m.||Feedjack||15.02.16||Release Created|
|April 18, 2015, 4:27 p.m.||Feedjack||15.02.17||Release Created|
|April 18, 2015, 4:27 p.m.||Feedjack||15.02.25||Release Created|
|April 18, 2015, 4:27 p.m.||Feedjack||15.02.30||Release Created|
|April 18, 2015, 4:27 p.m.||Feedjack||0.9.20||Release Created|
|April 18, 2015, 4:27 p.m.||Feedjack||0.9.18||Release Created|
|April 18, 2015, 4:27 p.m.||Feedjack||15.03.1||Release Created|
|April 18, 2015, 4:27 p.m.||Feedjack||15.03.0||Release Created|
|April 18, 2015, 4:27 p.m.||Feedjack||0.9.19||Release Created|
|April 18, 2015, 4:27 p.m.||Feedjack||0.9.16||Release Created|
|April 18, 2015, 4:27 p.m.||Feedjack||15.02.46||Release Created|
|April 18, 2015, 4:27 p.m.||Feedjack||15.02.45||Release Created|
|April 18, 2015, 4:27 p.m.||Feedjack||15.02.44||Release Created|
|April 18, 2015, 4:27 p.m.||Feedjack||15.02.43||Release Created|
|April 18, 2015, 4:27 p.m.||Feedjack||15.02.42||Release Created|
|April 18, 2015, 4:27 p.m.||Feedjack||Package Created|