Automatically share data between popular services you use on the web. And instead of giving your credentials to them, become the owner of yours !

For example a new RSS item is published, django-trigger-happy will be able to automatically create a note on your Evernote account or create a bookmark to your own Readability or Pocket account and so on

The goal of this project is to be independant from any other solution like IFTTT, CloudWork or others.

Thus you could host your own solution and manage your own triggers without depending any non-free solution.

With this project you can host triggers for you.

All you need is to have a hosting provider (or simply your own server ;) ) who permits to use a manager of tasks like "cron" and, of course Python.

• Python 3.4.x
• Django >= 1.8
• Celery <http://www.celeryproject.org/> == 3.1.18
• django-th-rss == 0.3.0
• django-th-pocket == 0.2.0
• django-js-reverse == 0.3.3
• django-redis-cache <https://pypi.python.org/pypi/django-redis-cache/> == 0.13.1
• django-redisboard <https://pypi.python.org/pypi/django-redisboard/> == 1.2.0

To get the project up and running, from your virtualenv, do:

git clone https://github.com/foxmask/django-th.git

To install the required modules, do:

pip install -r https://raw.githubusercontent.com/foxmask/django-th/master/requirements.txt

and at least :

cd django-th 
python manage.py syncdb
python manage.py runserver

to startup the database

As usual you will setup the database parameters.

Important parts are the settings of the available services :

add the module django_th to the INSTALLED_APPS

INSTALLED_APPS = (
     ...
     'formtools',
     'django_th', 
     'th_rss',
     'django_js_reverse',

then complet with its companion

'pocket',     # if you own your own pocket account
'th_pocket',  # if you own your own pocket account

TH_SERVICES is a list of the services we, like for example,

TH_SERVICES = (
    'th_rss.my_rss.ServiceRss',
    'th_pocket.my_pocket.ServicePocket',
)

from django.conf.urls import patterns, include, url
from django.contrib import admin

urlpatterns = patterns('',
     # Examples:
     # url(r'^$', 'th.views.home', name='home'),
     # url(r'^blog/', include('blog.urls')),

     url(r'^admin/', include(admin.site.urls)),
     url(r'', include('django_th.urls')),
)

For each TriggerHappy component, define one cache like below

# RSS Cache
'th_rss':
{
    'TIMEOUT': 500,
    "BACKEND": "django_redis.cache.RedisCache",
    "LOCATION": "127.0.0.1:6379",
    "OPTIONS": {
        "DB": 2,
        "CLIENT_CLASS": "django_redis.client.DefaultClient",
    }
},

# Twitter Cache
'th_twitter':
{
    'TIMEOUT': 500,
    "BACKEND": "django_redis.cache.RedisCache",
    "LOCATION": "127.0.0.1:6379",
    "OPTIONS": {
        "DB": 3,
        "CLIENT_CLASS": "django_redis.client.DefaultClient",
    }
},

Celery will handle tasks itself to populate the cache from provider services and then exploit it to publish the data to the expected consumer services

Define the broker then the scheduler

BROKER_URL = 'redis://localhost:6379/0'

CELERYBEAT_SCHEDULE = {
    'read-data': {
        'task': 'django_th.tasks.read_data',
        'schedule': crontab(minute='27,54'),
    },
    'publish-data': {
        'task': 'django_th.tasks.publish_data',
        'schedule': crontab(minute='59'),
    },
}

[program:django_th_worker]
user = foxmask
directory=/home/projects/trigger-happy/th
command=/home/projects/trigger-happy/bin/celery -A th worker --autoscale=10,3 -l info
autostart=true
autorestart=true
redirect_stderr=true
stdout_logfile=/home/projects/trigger-happy/logs/trigger-happy.log
stderr_logfile=/home/projects/trigger-happy/logs/trigger-happy-err.log

[program:django_th_beat]
user = foxmask
directory=/home/projects/trigger-happy/th
command=/home/projects/trigger-happy/bin/celery -A th beat -l info
autostart=true
autorestart=true
redirect_stderr=true
stdout_logfile=/home/projects/trigger-happy/logs/trigger-happy.log
stderr_logfile=/home/projects/trigger-happy/logs/trigger-happy-err.log

once the module is installed, go to the admin panel and activate the service you want. Currently there are 4 services, RSS, Evernote, Pocket and Readability.

All you can decide here is to tell if the service requires an external authentication or not.

Once they are activated....

... User can use them

The user activates the service for their own need. If the service requires an external authentication, he will be redirected to the service which will ask him the authorization to acces the user's account. Once it's done, goes back to django-trigger-happy to finish and record the "auth token".

a set of 3 pages will ask to the user information that will permit to trigger data from a service "provider" to a service "consummer".

For example :

• page 1 : the user gives a RSS feed
• page 2 : the user gives the name of the notebook where notes will be stored and a tag if he wants
• page 3 : the user gives a description

Here are the available management commands you can use by hand when you need to bypass the beat of Celery :

Available subcommands:

[django_th]
    fire_read_data     # will put date in cache
    fire_publish_data  # will read cache and publish data

To start handling the queue of triggers you/your users configured, just set those 2 management commands in a crontab or any other scheduler solution of your choice, if you dont want to use the beat of Celery

Also : Keep in mind to avoid to set a too short duration between 2 run to avoid to be blocked by the externals services (by their rate limitation) you/your users want to reach.

http://trigger-happy.readthedocs.org/

You can find all details of all existing services of the blog : http://www.foxmask.info/tag/TriggerHappy