Suivi des « ateliers Aircox » de la radio (vidéos, manuels, etc) : http://public.radiocampus.be/Aircox/
Go to file
2016-07-12 22:26:36 +02:00
cms schedule -- get queryset from routes.DateRoute 2016-07-11 11:43:26 +02:00
controllers liquidsoap: fix error in template, station.current_source on request's id 2016-07-12 22:26:36 +02:00
data logo; RelatedPost sync with related object 2016-05-22 17:43:13 +02:00
liquidsoap start app controllers that aims to replace liquidsoap on long term, and be more generic and reusable 2016-07-12 11:11:21 +02:00
programs start app controllers that aims to replace liquidsoap on long term, and be more generic and reusable 2016-07-12 11:11:21 +02:00
website schedule -- get queryset from routes.DateRoute 2016-07-11 11:43:26 +02:00
__init__.py move files 2015-12-22 08:37:17 +01:00
LICENSE move files 2015-12-22 08:37:17 +01:00
Manifest.in move files 2015-12-22 08:37:17 +01:00
notes.md liquidsoap: fix error in template, station.current_source on request's id 2016-07-12 22:26:36 +02:00
README.md doc 2016-06-02 01:37:19 +02:00
requirements.txt sound_monitor: filesystem monitoring using watchdog 2015-12-29 12:05:59 +01:00
setup.py move files 2015-12-22 08:37:17 +01:00

Platform to manage a radio, schedules, website, and so on. We use the power of Django and Liquidsoap.

Current features

  • streams: multiple random music streams when no program is played. We also can specify a time range and frequency;
  • diffusions: generate diffusions time slot for programs that have schedule informations. Check for conflicts and rerun.
  • liquidsoap: create a configuration to use liquidsoap as a stream generator. Also provides interface and control to it;
  • sounds: each programs have a folder where sounds can be put, that will be detected by the system. Quality can be check and reported for later use. Later, we plan to have uploaders to external plateforms. Sounds can be defined as excerpts or as archives.
  • cms: a small CMS to generate a website with all cool informations related to programs and diffusions. On the contrary of some other plateforms, we keep program and content management distinct.
  • log: keep a trace of every played/loaded sounds on the stream generator.

Applications

  • programs: managing stations, programs, schedules and diffusions. This is the core application, that handle most of the work;
  • liquidsoap: generate configuration and controls over liquidsoap. We use one instance of liquidsoap per station;
  • cms: cms manager with reusable tools (can be used in another website application);
  • website: set of common models, sections, and other items ready to be used for a website;

Installation

For now, we provide only applications availables under the aircox directory. Create a django project, and add the aircox applications directory.

Later we would provide a package, but now we have other priorities.

settings.py

  • There must be BASE_DIR or PROJECT_ROOT defined in order to make liquidsoap working (that must call manage.py using an absolute path).
  • INSTALLED_APPS:
    • dependencies: 'taggit' (programs and cms applications), 'easy_thumbnails' (cms), 'honeypot' (cms)
    • optional dependencies (in order to make users' life easier): 'autocomplete_light', 'suit'
    • aircox: 'aircox.programs', 'aircox.liquidsoap', 'aircox.cms', 'aircox.website'

urls.py

  • dependencies:

    url(r'^autocomplete/', include('autocomplete_light.urls')), # autocomplete
    
  • aircox:

     # if using liquidsoap
    url(r'^liquidsoap/', include('aircox.liquidsoap.urls')),