Re: EWA
0 views
Skip to first unread message
Jacob Smullyan
Jul 20, 2007, 12:04:47 PM7/20/07
to ewa-d...@googlegroups.com, Wolf Schwurack
On 7/20/07, Wolf Schwurack <wo...@uen.org> wrote:
You are also going to need lame, and make sure that ewa knows what path it lives at, if it isn't in /usr/bin.
A recent issue came up with ply, btw -- the latest version ply doesn't work with the ewa release. See the mailing list archive for discussion. I will soon (that is, eventually) produce a new ewa release with a bundled ply so we don't have this problem again.
The manual isn't very stylishly written, I confess, but does attempt to go over this. When you have more specific issues, it will be easier to address the gaps. I suggest starting with this rules.conf:
default
It does nothing, but if you get it to work, then you know you are getting somewhere.
You want to monitor ewa's logfile while you get this up to look for errors related to paths and permissions.
I'm stuck, with the Configuration files: ewa.conf and rule configuration. I have a Solaris server with EWA, Python, setuptools, simplejson, eyeD3, ply, flup , apache and nose install.
You are also going to need lame, and make sure that ewa knows what path it lives at, if it isn't in /usr/bin.
A recent issue came up with ply, btw -- the latest version ply doesn't work with the ewa release. See the mailing list archive for discussion. I will soon (that is, eventually) produce a new ewa release with a bundled ply so we don't have this problem again.
I downloaded a copy of the ewa.conf and change the keys for the path of rules.conf and the base audio. I'm not sure how to setup the rules.conf.
The manual isn't very stylishly written, I confess, but does attempt to go over this. When you have more specific issues, it will be easier to address the gaps. I suggest starting with this rules.conf:
default
It does nothing, but if you get it to work, then you know you are getting somewhere.
You want to monitor ewa's logfile while you get this up to look for errors related to paths and permissions.
Also once the configuration files are set, what do I do next? Does EWA replace Icecast and Darkice (on other servers) for the streaming? Or is this an add-on so we can have intro file for the streaming?
It replaces Icecast. EWA was written as a backend for an http server like lighttpd. This can be used for streaming -- just serve a playlist (.m3u, .pls, .ram, .asx, what have you) with http links in it -- or for downloading. I see the use case for icecast and the like being continuous streams that you join in progress; for distinct files served on demand, a plain ole http server works just fine.
If you use lighttpd, you will suffer less in setting this up, because it has been done before. Apache *should* work with mod_sendfile, but I haven't done it. If you try it that way, let me know how it goes!
Cheers,
Jacob S.
If you use lighttpd, you will suffer less in setting this up, because it has been done before. Apache *should* work with mod_sendfile, but I haven't done it. If you try it that way, let me know how it goes!
Cheers,
Jacob S.
Reply all
Reply to author
Forward
0 new messages