A radio automation based on MPD.

boyska 0036750004 minor doc/debug improvement 8 سال پیش
doc bf7927b0e4 doc about mpd socket configuration 9 سال پیش
larigira 0036750004 minor doc/debug improvement 8 سال پیش
.gitignore 2c7e0bdf70 Nicer DB list, bootstrap 9 سال پیش
MANIFEST.in bf557d789b FIX larigira.dbadmin packaging 9 سال پیش
README.rst 6f0c335d2d s/ejdb/tinydb, clear eventmodel, some testing 9 سال پیش
conftest.py 2bc118bfd9 http testing 9 سال پیش
requirements.txt 6f9e4b199b SIGHUP, use mpd connection without subcommand 9 سال پیش
setup.py 27ca7fac03 default DB_URI = ~/.config/larigira/db.json 9 سال پیش

README.rst

=========
larigira
=========

About
-------

A radio automation based on MPD. Larigira will sit right to your mpd player and
will keep your playlist never empty. It will also manage a db of "events", so
that you can schedule shows, play jingles every X minutes, etc.

Software stack
---------------

* MPD, of course
* python2
* gevent as an async framework
* flask to provide web interface and rpc
* tinydb as an embedded database

Why? (aka design features)
--------------------------

Reinventing a player is a bad idea. MPD provides an eccellent base.

Separating the player from "action loops" makes it easy to work on this. For
example, you can stop larigira for some minutes, and the audio will keep
playing. It also means that you can easily replace specific parts of your radio
automation.

The "continous playing" part is separated from the "events" part. ``larigira``
can be run to perform one, the other, or both.

The "audio generation" part can be used separately by any script that you like.

Installation
-------------

Just run ``python setup.py install``. It will, of course, also work in a
virtualenv. Apart from running an MPD server, there is no additional setup.

You will find some command in your PATH now; they all begin with ``larigira``,
so the usual ```` is a good way to explore them ;)

The name
---------

larigira mai la sbaglia...

-- https://www.youtube.com/watch?v=K9XJkOSSdEA