X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~mdw/git/disorder/blobdiff_plain/9025afab24cdcb04dffe8af35491a04087f1cde0..9f28e855aad11d25c0a69a7e59825c07bdefcafe:/README diff --git a/README b/README index 9c6150f..b61ac7a 100644 --- a/README +++ b/README @@ -15,9 +15,9 @@ DisOrder is a multi-user software jukebox. See CHANGES for details of recent changes to DisOrder. -The server supports Linux and can be made to on a Mac. The clients work on -both Linux and the Mac. It could probably be ported to some other UNIX -variants in without too much effort. Things you will need: +The server supports Linux and can be made to on a Mac (see README.mac). The +clients work on both Linux and the Mac. It could probably be ported to some +other UNIX variants without too much effort. Things you will need: Build dependencies: Name Tested Notes @@ -32,6 +32,7 @@ Build dependencies: libFLAC 1.1.2 GNU C 4.1.2 GNU Make 3.81 + GNU Sed 4.1.5 Python 2.4.4 (optional) GTK+ 2.8.20 (if you want the GTK+ client) GLIB 2.12.4 (if you want the GTK+ client) @@ -90,16 +91,12 @@ NOTE: If you are upgrading from an earlier version, see README.upgrades. See README.client for setting up a standalone client (or read the disobedience man page). - The server is only built by default under Linux. See README.mac concerning - its use under OS X. - 2. Install it. Most of the installation is done via the install target: make installdirs install - The CGI interface has to be installed separately: - - install -m 755 clients/disorder.cgi /usr/local/lib/cgi-bin/disorder + The CGI interface has to be installed separately; see under 'Web Interface' + below. 3. Create a 'jukebox' user and group, with the jukebox group being the default group of the jukebox user. The server will run as this user and group. @@ -111,24 +108,25 @@ NOTE: If you are upgrading from an earlier version, see README.upgrades. specifically for DisOrder. 4. Create /etc/disorder/config. Start from examples/config.sample and adapt it - to your own requirements. In particular, you should: - * add 'player' commands for any file formats not supported natively + to your own requirements. The things you MUST do are: * edit the 'collection' command to identify the location(s) of your own digital audio files. These commands also specify the encoding of filenames, which you should be sure to get right as recovery from an error here can be painful (see BUGS). + Optionally you may also want to do the following: + * add 'player' commands for any file formats not supported natively * edit the 'scratch' commands to supply scratch sounds (or delete them if you don't want any). - * edit the 'trust' command to reflect the user the web interface will - eventually run as. - * edit the 'url' command to give the URL of the web interface. * add or remove 'stopword' entries as necessary (these words won't take part in track name searches from the web interface). See disorder_config(5) for more details. - See README.raw for details on setting up "raw format" players, which allow - for pausing and gapless play. + See README.streams for how to set up network play. + + If adding new 'player' commands, see README.raw for details on setting up + "raw format" players. Non-raw players are still supported but not in all + configurations and they cannot support pausing and gapless play. 5. Make sure the server is started at boot time. @@ -182,9 +180,8 @@ These instructions assumes you are using Apache 1.3.x. You need to configure a number of things to make this work: -1. If you want to have a 'jukebox' virtual host, modify the DNS (or hosts file - if you are somehow reading this in the 1980s) accordingly and use a fragment - such as this one: +1. If you want to have a 'jukebox' virtual host, modify the DNS accordingly and + use a fragment such as this one: DocumentRoot /home/jukebox/public_html @@ -229,19 +226,22 @@ You need to configure a number of things to make this work: # htpasswd -b /home/jukebox/http.users othername otherpass Adding password for user othername -4. The jukebox must be configured to trust the web user. I added the following - line to my /etc/disorder/config: +4. The jukebox must be configured to trust the web user. The example + configuration assumes that this is www-data, but it might be something else + on your system. Edit the 'trust' line if necessary. - trust www-data +5. Install disorder.cgi in an appropriate location. Remember to make it + executable. For example: - This might not be the same on your system! You have to specify the user - that the CGI script runs as, whatever that is. + install -m 755 clients/disorder.cgi ~jukebox/public_html/index.cgi -5. Install disorder.cgi in an appropriate location. Remember to make it - executable. With the above configuration I installed it as - ~jukebox/public_html/index.cgi. +6. The config file must also allow the web interface to be any user, and it + must list the URL of the web interface explicitly: -6. Give www-data (or whatever user it is) a password and edit + trust www-data + url http://jukebox.DOMAIN/ + +7. Give www-data (or whatever user it is) a password and edit /etc/disorder/config.private accordingly. This file should be mode 640 and owned by root:jukebox. The line should look something like this: @@ -251,24 +251,19 @@ You need to configure a number of things to make this work: disorder reconfigure -7. Teach www-data its password, by putting it in /etc/disorder/config.www-data. +8. Teach www-data its password, by putting it in /etc/disorder/config.www-data. This file should be mode 640 and owned by root:www-data. password MYPASSWORD (You could also use ~www-data/.disorder/passwd for this but on some systems the web server user's home directory is inside the document root, which - would have rather unfortunate consequences.) + would have rather unfortunate consequences!) -8. Try it out. You should be asked for a username and password that you +9. Try it out. You should be asked for a username and password that you configured earlier, and be shown details of what is playing and what other tracks have been configured for future play. -9. Some features take time to start working, for instance those involving - reporting the length of tracks. This is because the server starts up as - quickly as possible even if the full track data has not yet been gathered; - the track data is then calculated in the background. - 10. If you run into problems, always look at the appropriate error log; the message you see in your web browser will usually not be sufficient to diagnose the problem all by itself.