Hi Romain, Of cause building a debian knowledge would bring a lot of advantages like resolving package dependencies and setup of user and file permissions.
Unfortunately I have no knowledge at all of building a debian package, I dont even know how to build a make file. If you would like to work on this or share your knowledge about, I would be happy of cause, could learn from this and I am open for any input, e.g on following topics. Basically I see 2 independent packages, one for the scheduler and one for synchronization. The released source and target plug-ins are only a subset of possible synchronization interfaces. All input and output plugins can be combined with each other. There is room for improvement like ical or RSS/Atom feed input plug-ins. I have done basic implemented of more targets that are not yet part of the current release: output to another google calendar and calcms output (our broadcast description solution) to publish google calendar events (that describe broadcasts using wiki syntax) to calcms ) at any CMS, like here in drupal: http://piradio.de/programm/sendungen/2011-06-22.html . That is why I would like to separate scheduler and synchronization components. Another topic is choosing the user to run the scheduler. Today I use a common user for liquidsoap and the scheduler. Maybe its a good idea not to create a new user for the scheduler, but to run it as user liquidsoap instead. Files of the web application should be owned by the the web server user is running at. Some files should be shared between web user and scheduler user to monitor liquidsoap/scheduler status at web and to trigger synchronization. Today this is solved by setting the user to the scheduler user and setting the group to the web group (www-data). I am not sure what the best solution would be and if these points could be setup at time of installation, so the user would not need to take care of all of this. BR, Peter Am 07.06.2011 15:55, schrieb Romain Beauxis: > Hi Peter! > > 2011/6/5 Peter Retep<[email protected]>: >> Hi, >> >> As mentioned some time ago, I have written a stream-switch scheduler, based >> on liquidsoap. >> I would like to share the current version by this mail. >> >> The scheduler can be used to switch between live audio streams at a >> givendate and time. >> Date and time of a switch (start of starting a broadcast) can be dynamically >> (re)configured while scheduler and liquidsoap are running. >> >> There is a google calendar integration which allows you to define when which >> station (or stream URL) will be played. >> For each station you can define a stream URL and multiple aliases which can >> be used at the Google Calendar to address the station. >> If a second stream URL is given it will be used as fallback for the first >> one. >> The scheduler itself should run in the background and communicate with >> liquidsoap via telnet interface. >> >> Furthermore there is a web GUI which shows you the scheduler status or >> initiates manual synchronization with the Google Calendar. >> It should furthermore warn you on invalid URLs, missing processes running >> (scheduler, liquidsoap) and much more. >> >> We use the scheduler now for some weeks for receiving streams of 3 different >> stations at the city and put the current scheduled one to be played at the >> FM transmitter station. >> You could also use it for schedule listening to your radio, like play >> station A from 2 till 3, then play station B from 2 till 4, etc. >> The scheduler does not work with any files or playlists and can be used for >> audio streams only (input.http). >> >> You can find all of it here: >> http://dev.radiopiloten.de/dokuwiki/doku.php/liquidsoap:scheduler > Thanks for this work, it is very impressive! > > I am wondering if you would like to make a debian package out of it? I > would be pleased to work on that.. :-) > > Romain > ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
