Run local actions when new items are added to MixCloud.

Example uses include:

• Autoplay newly published things in a new browser window
• Send a notification email
• Feed item to an IM bot
• Tweet a link

Why? Because...

1. I kept missing new uploads by my favourite DJ
2. The MixCloud API makes it easy

You'll probably want to run this from a cron, so it has built-in locking to ensure no more than one instance runs at once.

• Python 3 & (probably included) pyvenv. On OSX with homebrew, brew install python3

• Record successful processing so that item won't be touched again
• Retry failed actions on the next run
• Limit to N most recent items

Needs a virtualenv and a few requirements.

$ cd mixcloud-trigger
$ pyvenv _venv3/
$ . _venv3/bin/activate
$ pip install --upgrade pip
$ pip install -r code/requirements.txt

Supports .ini files plus include dirs so config is easy to manage & machine-generate.

Example config tree:

$ tree conf
conf
├── main.conf
└── sources
    └── outsidetrance.conf
    
$ cat cat conf/main.conf
[sources]
sources_dir = conf/sources/

[metadata]
metadata_path = data/

$ cat conf/sources/outsidetrance.conf
[outsidetrance]
item_action = /bin/echo -n {name}
max_items = 3

Global config follows the format:

Per-source config must be:

• Within the sources_dir directory. It is not valid to store per-source config in the main config file.
• Filename ending with .conf
• In a section headed with the source name

Inside, the following fields are valid:

Python's String.format() is used to interpolate variables into your command for the specific feed item. Variables are:

Variables are escaped with shlex.quote(). Your command isn't; be careful with it.

Anything /bin/sh can handle, item_action can handle. Your action is written to a temporary file and passed to the local /bin/sh for execution. This means...

• ; can be used to separate multiple commands. e.g. cd /path/to/somewhere; do_something_with {url}
• Pipes work just fine
• Environment vars work - e.g. cd $HOME; do_something_with {url}
• sudo if you want to, but secure it properly

Python's subprocess module has problems handling very large amounts of output from a command. This includes basically anything that prints a progress bar. If you're calling some utility and it has a --quiet option, try to use it.

TBA.

$ tree conf
conf
├── main.conf
└── sources
    └── outsidetrance.conf

$ . _venv3/bin/activate

(_venv3) $ ./code/mixtrig.py -h    # display help

(_venv3) $ ./code/mixtrig.py -c examples/conf/main.conf

• To ensure no item gets processed twice, once handled media item keys are written to a small SQLite DB is maintained under data/. I tried a simpler approach (ignoring anything from before the script's last run) but it seems there's sometimes a delay between media uploads and the item becoming available, and this meant unseen items could fall before the script's previous run.
• Coloured/indented output with clint
• Some test coverage via basic Python unittest module

• MixCloud's API returns 20 items per page and we don't yet support pagination. Thus if there are more than 20 new items since the last scrape (and you set max_items > 20), the oldest ones will be overlooked.

$ python -m unittest discover code/

• Better input-checking on config
• Make all_action work
• Mutleythreading for shell actions

Yes please!

GPLv3.