Icecast Streaming Media Server

[Guest]

Help File documentation for this configuration item is limited to the following:

fileserve
This flag turns on the icecast2 fileserver from which static files can be served. All files are served relative to the path specified in the <paths><webroot> configuration setting.

Do I understand this to mean when the Icecast fileserver setting is configured/turned on, that it acts to serve Icecast with static files (similar to Icecast source clients creating the stream input)?

If so, how are the static files listed in the configuration file so that they can be streamed?

Can a M3U playlist file be used with fileserve in lieu of listing individual files? (I have 5 playlists of 5 seminar lessons each that I want to stream.)

If fileserve is turned off, does this disable the static file(s) listed as mount-fallback(s) and/or other static files used in the configuration file?

Does the setting follow other config usage: '0' = off, '1' = on?

TIA for any further documentation or help with this setting!

-Tertius

[karlH]

The fileserver engine is just that, it writes the requested file to the client, much like apache or any other web server does. There's no rate bitrate regulation based on the format of the file.

The files don't have to be listed, they are requested based upon the requested entity based off webroot. You can list them as <mount> in the xml file if you want to apply authentication to a particular file.

m3u/pls etc can be created in webroot even overriding the automatically generated one for existing streams. You can tailor it to your setup. Only m3u and xsl have special significance within webroot, all other files as transferred as-is.

If fileseve is disable, fallback to file will still work as normal, but any request to get a file from icecast will be blocked.

The configuration takes a 0 or 1 like all other boolean settings within icecast.

karl.