chiark / gitweb /
ignore tarballs
[disorder] / doc / disorder_config.5.in
CommitLineData
460b9539 1.\"
405fea4e 2.\" Copyright (C) 2004, 2005, 2006, 2007 Richard Kettlewell
460b9539 3.\"
4.\" This program is free software; you can redistribute it and/or modify
5.\" it under the terms of the GNU General Public License as published by
6.\" the Free Software Foundation; either version 2 of the License, or
7.\" (at your option) any later version.
8.\"
9.\" This program is distributed in the hope that it will be useful, but
10.\" WITHOUT ANY WARRANTY; without even the implied warranty of
11.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
12.\" General Public License for more details.
13.\"
14.\" You should have received a copy of the GNU General Public License
15.\" along with this program; if not, write to the Free Software
16.\" Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
17.\" USA
18.\"
19.TH disorder_config 5
20.SH NAME
21pkgconfdir/config - DisOrder jukebox configuration
22.SH DESCRIPTION
23The purpose of DisOrder is to organize and play digital audio files, under the
24control of multiple users. \fIpkgconfdir/config\fR is the primary
25configuration file but this man page currently documents all of its various
26configuration files.
27.SS Tracks
28DisOrder can be configured with multiple collections of tracks, indexing them
29by their filename, and picking players on the basis of filename patterns (for
30instance, "*.mp3").
31.PP
32Although the model is of filenames, it is not inherent that there are
33corresponding real files - merely that they can be interpreted by the chosen
34player. See \fBdisorder\fR(3) for more details about this.
35.PP
36Each track can have a set of preferences associated with it. These are simple
37key-value pairs; they can be used for anything you like, but a number of keys
38have specific meanings. See \fBdisorder\fR(1) for more details about these.
39.SS "Track Names"
40Track names are derived from filenames under the control of regular
41expressions, rather than attempting to interpret format-specific embedded name
42information. They can be overridden by setting preferences.
43.PP
44Names for display are distinguished from names for sorting, so with the right
45underlying filenames an album can be displayed in its original order even if
46the displayed track titles are not lexically sorted.
47.SS "Server State"
48A collection of global preferences define various bits of server state: whether
49random play is enabled, what tags to check for when picking at random, etc.
50.SS "Users And Access Control"
51DisOrder distinguishes between multiple users. This is for access control and
52reporting, not to provide different views of the world: i.e. preferences and so
53on are global.
54.PP
55It's possible to restrict a small number of operations to a specific subset of
56users. However, it is assumed that every user is supposed to be able to do
57most operations - since the users are all sharing the same audio environment
58they are expected to cooperate with each other.
59.PP
60Access control is entirely used-based. If you configure DisOrder to listen for
61TCP/IP connections then it will accept a connection from anywhere provided the
62right password is available. Passwords are never transmitted over TCP/IP
63connections in clear, but everything else is. The expected model is that
64host-based access control is imposed at the network layer.
65.SS "Web Interface"
66The web interface is controlled by a collection of template files, one for each
67kind of page, and a collection of option files. These are split up and
68separate from the main configuration file to make it more convenient to
69override specific bits.
70.PP
71The web interface connects to the DisOrder server like any other user, though
72it is given a special privilege to "become" any other user. (Thus, any process
73with the same UID as the web interface is very powerful as far as DisOrder
74goes.)
75.PP
76Access control to the web interface is (currently) separate from DisOrder's own
77access control (HTTP authentication is required) but uses the same user
78namespace.
79.SH "CONFIGURATION FILE"
80.SS "General Syntax"
81Lines are split into fields separated by whitespace (space, tab, line
82feed, carriage return, form feed). Comments are started by the number
83sign ("#").
84.PP
85Fields may be unquoted (in which case they may not contain spaces and
86may not start with a quotation mark or apostrophe) or quoted by either
87quotation marks or apostrophes. Inside quoted fields every character
88stands for itself, except that a backslash can only appear as part of
89one of the following escape sequences:
90.TP
91.B \e\e
92Backslash
93.TP
94.B \e"
95Quotation mark
96.\" "
97.TP
98.B \e'
99Apostrophe
100.TP
101.B \en
102Line feed
103.PP
104No other escape sequences are allowed.
105.PP
106Within any line the first field is a configuration command and any
107further fields are parameters. Lines with no fields are ignored.
108.PP
109After editing the config file use \fBdisorder reconfigure\fR to make
110it re-read it. If there is anything wrong with it the daemon will
111record a log message and ignore the new config file. (You should fix
112it before next terminating and restarting the daemon, as it cannot
113start up without a valid config file.)
114.SS "Global Configuration"
115.TP
116.B home \fIDIRECTORY\fR
117The home directory for state files. Defaults to
118.IR pkgstatedir .
119.TP
120.B plugin \fIPATH\fR
121Adds a directory to the plugin path. (This is also used by the web
122interface.)
123.IP
124Plugins are opened the first time they are required and never after,
125so after changing a plugin you must restart the server before it is
126guaranteed to take effect.
127.SS "Server Configuration"
128.TP
129.B alias \fIPATTERN\fR
130Defines the pattern use construct virtual filenames from \fBtrackname_\fR
131preferences.
132.IP
133Most characters stand for themselves, the exception being \fB{\fR which is used
134to insert a track name part in the form \fB{\fIname\fB}\fR or
135\fB{/\fIname\fB}\fR.
136.IP
137The difference is that the first form just inserts the name part while the
138second prefixes it with a \fB/\fR if it is nonempty.
139.IP
140The pattern should not attempt to include the collection root, which is
141automatically included, but should include the proper extension.
142.IP
143The default is \fB{/artist}{/album}{/title}{ext}\fR.
144.TP
145.B channel \fICHANNEL\fR
146The mixer channel that the volume control should use. Valid names depend on
147your operating system and hardware, but some standard ones that might be useful
148are:
149.RS
150.TP 8
151.B pcm
152Output level for the audio device. This is probably what you want.
153.TP
154.B speaker
155Output level for the PC speaker, if that is connected to the sound card.
156.TP
157.B pcm2
158Output level for alternative codec device.
159.TP
160.B vol
161Master output level. The OSS documentation recommends against using this, as
162it affects all output devices.
163.RE
164.IP
165You can also specify channels by number, if you know the right value.
166.TP
167.B collection \fIMODULE\fR \fIENCODING\fR \fIROOT\fR
168Define a collection of tracks.
169.IP
170\fIMODULE\fR defines which plugin module should be used for this
171collection. Use the supplied \fBfs\fR module for tracks that exists
172as ordinary files in the filesystem.
173.IP
174\fIENCODING\fR defines the encoding of filenames in this collection.
175For \fBfs\fR this would be the encoding you use for filenames.
176Examples might be \fBiso-8859-1\fR or \fButf-8\fR.
177.IP
178\fIROOT\fR is the root in the filesystem of the filenames and is
179passed to the plugin module.
180.TP
181.B device \fINAME\fR
182ALSA device to play raw-format audio. Default is \fBdefault\fR, i.e. to use
183the whatever the ALSA configured default is.
184.TP
185.B gap \fISECONDS\fR
186Specifies the number of seconds to leave between tracks. The default
187is 2.
188.TP
189.B history \fIINTEGER\fR
190Specifies the number of recently played tracks to remember (including
191failed tracks and scratches).
192.TP
193.B listen \fR[\fIHOST\fR] \fISERVICE\fR
194Listen for connections on the address specified by \fIHOST\fR and port
195specified by \fISERVICE\fR. If \fIHOST\fR is omitted then listens on all
196local addresses.
197.IP
198Normally the server only listens on a UNIX domain socket.
199.TP
200.B lock yes\fR|\fBno
201Determines whether the server locks against concurrent operation. Default is
202\fByes\fR.
203.TP
204.B mixer \fIPATH\fR
205The path to the mixer device, if you want access to the volume control,
206e.g. \fB/dev/mixer\fR.
207.TP
208.B namepart \fIPART\fR \fIREGEXP\fR \fISUBST\fR [\fICONTEXT\fR [\fIREFLAGS\fR]]
209Determines how to extract trackname part \fIPART\fR from a
210track name (with the collection root part removed).
211Used in \fB@recent@\fR, \fB@playing@\fR and \fB@search@\fR.
212.IP
213Track names can be different in different contexts. For instance the sort
214string might include an initial track number, but this would be stripped for
215the display string. \fICONTEXT\fR should be a glob pattern matching the
216contexts in which this directive will be used.
217.IP
218Valid contexts are \fBsort\fR and \fBdisplay\fR.
219.IP
220All the \fBnamepart\fR directives are considered in order. The
221first directive for the right part, that matches the desired context,
222and with a \fIREGEXP\fR that
223matches the track is used, and the value chosen is constructed from
224\fISUBST\fR according to the substitution rules below.
225.IP
226Note that searches use the raw track name and \fBtrackname_\fR preferences but
227not (currently) the results of \fBnamepart\fR, so generating words via this option
228that aren't in the original track name will lead to confusing results.
229.IP
230If you supply no \fBnamepart\fR directives at all then a default set will be
231supplied automatically. But if you supply even one then you must supply all of
232them. See the example config file for the defaults.
233.TP
234.B nice_rescan \fIPRIORITY\fR
235Set the recan subprocess priority. The default is 10.
236.IP
237(Note that higher values mean the process gets less CPU time; UNIX priority
238values are the backwards.)
239.TP
240.B nice_server \fIPRIORITY\fR
241Set the server priority. This is applied to the server at startup time (and
242not when you reload configuration). The server does not use much CPU itself
243but this value is inherited by programs it executes. If you have limited CPU
244then it might help to set this to a small negative value. The default is 0.
245.TP
246.B nice_speaker \fIPRIORITY\fR
247Set the speaker process priority. This is applied to the speaker process at
248startup time (and not when you reload the configuration). The speaker process
249is not massively CPU intensive by today's standards but depends on reasonably
250timely scheduling. If you have limited CPU then it might help to set this to a
251small negative value. The default is 0.
252.TP
253.B player \fIPATTERN\fR \fIMODULE\fR [\fIOPTIONS.. [\fB--\fR]] \fIARGS\fR...
254Specifies the player for files matching the glob \fIPATTERN\fR. \fIMODULE\fR
255specifies which plugin module to use.
256.IP
257The following options are supported:
258.RS
259.TP
260.B --wait-for-device\fR[\fB=\fIDEVICE\fR]
261Waits (for up to a couple of seconds) for the default, or specified, libao
262device to become openable.
263.TP
264.B --
265Defines the end of the list of options. Needed if the first argument to the
266plugin starts with a "-".
267.RE
268.IP
269The following are the standard modules:
270.RS
271.TP
272.B exec \fICOMMAND\fR \fIARGS\fR...
273The command is executed via \fBexecvp\fR(3), not via the shell.
274The \fBPATH\fR environment variable is searched for the executable if it is not
275an absolute path.
276The command is expected to know how to open its own sound device.
277.TP
278.B execraw \fICOMMAND\fR \fIARGS\fR...
279Identical to the \fBexec\fR except that the player is expected to use the
280DisOrder raw player protocol (see notes below).
281.TP
282.B shell \fR[\fISHELL\fR] \fICOMMAND\fR
283The command is executed using the shell. If \fISHELL\fR is specified then that
284is used, otherwise \fBsh\fR will be used. In either case the \fBPATH\fR
285environment variable is searched for the shell executable if it is not an
286absolute path. The track name is stored in the environment variable
287\fBTRACK\fR.
288.IP
289Be careful of the interaction between the configuration file quoting rules and
290the shell quoting rules.
291.RE
292.IP
293If multiple player commands match a track then the first match is used.
294.TP
295.B prefsync \fISECONDS\fR
296The interval at which the preferences log file will be synchronised. Defaults
297to 3600, i.e. one hour.
298.TP
405fea4e 299.B sample_format \fIBITS\fB/\fIRATE\fB/\fICHANNELS
300Describes the sample format expected by the \fBspeaker_command\fR (below). The
301components of the format specification are as follows:
302.RS
303.TP 10
304.I BITS
305The number of bits per sample. Optionally, may be suffixed by \fBb\fR or
306\fBl\fR for big-endian and little-endian words. If neither is used the native
307byte order is assumed.
308.TP
309.I RATE
310The number of samples per second.
311.TP
312.I CHANNELS
313The number of channels.
314.PP
315The default is
316.BR 16/44100/2 .
317.RE
318.TP
460b9539 319.B signal \fINAME\fR
320Defines the signal to be sent to track player process groups when tracks are
321scratched. The default is \fBSIGKILL\fR.
322.IP
323Signals are specified by their full C name, i.e. \fBSIGINT\fR and not \fBINT\fR
324or \fBInterrupted\fR or whatever.
325.TP
405fea4e 326.B speaker_command \fICOMMAND
327Causes the speaker subprocess to pipe audio data into shell command
328\fICOMMAND\fR, rather than writing to a local sound card. The sample format is
329determine by
330.B sample_format
331above.
77cfc7a2 332.IP
333Note that if the sample format is wrong then
334.BR sox (1)
335is invoked to translate it. If
336.B sox
337is not installed then this will not work.
405fea4e 338.TP
460b9539 339.B restrict \fR[\fBscratch\fR] [\fBremove\fR] [\fBmove\fR]
340Determine which operations are restricted to the submitter of a
341track. By default, no operations are restricted, i.e. anyone can
342scratch or remove anything.
343.IP
344If \fBrestrict scratch\fR or \fBrestrict remove\fR are set then only the user
345that submitted a track can scratch or remove it, respectively.
346.IP
347If \fBrestrict move\fR is set then only trusted users can move tracks around in
348the queue.
349.IP
350If \fBrestrict\fR is used more than once then only the final use has any
351effect.
352.TP
353.B scratch \fIPATH\fR
354Specifies a scratch. When a track is scratched, a scratch track is
355played at random.
356Scratches are played using the same logic as other tracks.
357.IP
358At least for the time being, path names of scratches must be encoded using
359UTF-8 (which means that ASCII will do).
360.TP
361.B stopword \fIWORD\fR ...
362Specifies one or more stopwords that should not take part in searches
363over track names.
364.SS "Client Configuration"
365.TP
366.B connect \fR[\fIHOST\fR] \fISERVICE\fR
367Connect to the address specified by \fIHOST\fR and port specified by
368\fISERVICE\fR. If \fIHOST\fR is omitted then connects to the local host.
369Normally the UNIX domain socket is used instead.
370.SS "Web Interface Configuration"
371.TP
372.B refresh \fISECONDS\fR
373Specifies the maximum refresh period in seconds. Default 15.
374.TP
375.B templates \fIPATH\fR ...
376Specifies the directory containing templates used by the web
377interface. If a template appears in more than one template directory
378then the one in the earliest directory specified is chosen.
379.IP
380See below for further details.
381.TP
382.B transform \fITYPE\fR \fIREGEXP\fR \fISUBST\fR [\fICONTEXT\fR [\fIREFLAGS\fR]]
383Determines how names are sorted and displayed in track choice displays.
384.IP
385\fITYPE\fR is the type of transformation; usually \fBtrack\fR or
386\fBdir\fR but you can define your own.
387.IP
388\fICONTEXT\fR is a glob pattern matching the context. Standard contexts are
389\fBsort\fR (which determines how directory names are sorted) and \fBdisplay\fR
390(which determines how they are displayed). Again, you can define your
391own.
392.IP
393All the \fBtransform\fR directives are considered in order. If
394the \fITYPE\fR, \fIREGEXP\fR and the \fICONTEXT\fR match
395then a new track name is constructed from
396\fISUBST\fR according to the substitution rules below. If several
397match then each is executed in order.
398.IP
399If you supply no \fBtransform\fR directives at all then a default set will be
400supplied automatically. But if you supply even one then you must supply all of
401them. See the example config file for the defaults.
402.TP
403.B url \fIURL\fR
404Specifies the URL of the web interface. This URL will be used in
405generated web pages.
406.IP
407This must be the full URL, e.g. \fBhttp://myhost/cgi-bin/jukebox\fR and not
408\fB/cgi-bin/jukebox\fR.
409.SS "Authentication Configuration"
410.TP
411.B allow \fIUSERNAME\fR \fIPASSWORD\fR
412Specify a username/password pair.
413.TP
414.B password \fIPASSWORD\fR
415Specify password.
416.TP
417.B trust \fIUSERNAME\fR
418Allow \fIUSERNAME\fR to perform privileged operations such as shutting
419down or reconfiguring the daemon, or becoming another user.
420.TP
421.B user \fIUSER\fR
422Specifies the user to run as. Only makes sense if invoked as root (or
423the target user).
424.TP
425.B username \fIUSERNAME\fR
426Specify username. The default is taken from the environment variable
427\fBLOGNAME\fR.
428.PP
429Configuration files are read in the following order:
430.TP
431.I pkgconfdir/config
432.TP
433.I pkgconfdir/config.private
434Should be readable only by the jukebox group, and contain \fBallow\fR
435commands for authorised users.
436.TP
437.I pkgconfdir/config.\fRUSER
438Per-user system-controlled client configuration. Optional but if it
439exists must be readable only by the relevant user. Would normally
440contain a \fBpassword\fR directive.
441.TP
442.I ~\fRUSER\fI/.disorder/passwd
443Per-user client configuration. Optional but if it exists must be
444readable only by the relevant user. Would normally contain a
445\fBpassword\fR directive.
446.SH "GLOBAL PREFERENCES"
447These are the values set with \fBset-global\fR.
448.TP
449.B required-tags
450If this is set an nonempty then randomly played tracks will always have at
451least one of the listed tags.
452.IP
453Tags can contain any printing character except comma. Leading and trailing
454spaces are not significant but internal spaces are. Tags in a list are
455separated by commas.
456.TP
457.B prohibited-tags
458If this is set an nonempty then randomly played tracks will never have any of
459the listed tags.
460.TP
461.B playing
462If unset or \fByes\fR then play is enabled. Otherwise it is disabled. Use
463\fBdisable\fR rather than setting it directly.
464.TP
465.B random-play
466If unset or \fByes\fR then random play is enabled. Otherwise it is disabled.
467Use \fBdisable\fR rather than setting it directly.
468.SH "LIBAO DRIVER"
469.SS "Raw Protocol Players"
470Raw protocol players are expected to use the \fBdisorder\fR libao driver.
471Programs that use libao generally have command line options to select the
472driver and pass options to it.
473.SS "Driver Options"
474The known driver options are:
475.TP
476.B fd
477The file descriptor to write to. If this is not specified then the driver
478looks like the environment variable \fBDISORDER_RAW_FD\fR. If that is not set
479then the default is 1 (i.e. standard output).
480.TP
481.B fragile
482If this is set to a nonzero value then the driver will call \fB_exit\fR(2) if a
483write to the output file descriptor fails. This is a workaround for buggy
484players such as \fBogg123\fR that ignore write errors.
485.SH "WEB TEMPLATES"
486When \fBdisorder.cgi\fR wants to generate a page for an action it searches the
487directories specified with \fBtemplates\fR for a matching file. It is
488suggested that you leave the distributed templates unchanged and put
489any customisations in an earlier entry in the template path.
490.PP
491The supplied templates are:
492.TP
493.B about.html
494Display information about DisOrder.
495.TP
496.B choose.html
497Navigates through the track database to choose a track to play. The
498\fBdir\fR argument gives the directory to look in; if it is missing
499then the root directory is used.
500.TP
501.B choosealpha.html
502Provides a front end to \fBchoose.html\fR which allows subsets of the top level
503directories to be selected by initial letter.
504.TP
505.B playing.html
506The "front page", which usually shows the currently playing tracks and
507the queue.
508Gets an HTTP \fBRefresh\fR header.
509.IP
510If the \fBmgmt\fR CGI argument is set to \fBtrue\fR then we include extra
511buttons for moving tracks up and down in the queue. There is some logic in
512\fBdisorder.cgi\fR to ensure that \fBmgmt=true\fR is preserved across refreshes
513and redirects back into itself, but URLs embedded in web pages must include it
514explicitly.
515.TP
516.B prefs.html
517Views preferences. If the \fBfile\fR, \fBname\fR and \fBvalue\fR arguments are
518all set then that preference is modified; if \fBfile\fR and \fBname\fR are set
519but not \fBvalue\fR then the preference is deleted.
520.TP
521.B recent.html
522Lists recently played tracks.
523.TP
524.B search.html
525Presents search results.
526.TP
527.B volume.html
528Primitive volume control.
529.PP
530Additionally, other standard files are included by these:
531.TP
532.B credits.html
533Included at the end of the main content \fB<DIV>\fR element.
534.TP
535.B sidebar.html
536Included at the start of the \fB<BODY>\fR element.
537.TP
538.B stdhead.html
539Included in the \fB<HEAD>\fR element.
540.TP
541.B stylesheet.html
542Contains the default DisOrder stylesheet. You can override this by editing the
543CSS or by replacing it all with a \fB<LINK>\fR to an external stylesheet.
544.PP
545Templates are ASCII files containing HTML documents, with an expansion
546syntax to enable data supplied by the implementation to be inserted.
547.PP
548If you want to use characters outside the ASCII range, use either the
549appropriate HTML entity, e.g. \fB&eacute;\fR, or an SGML numeric
550character reference, e.g. \fB&#253;\fR. Use \fB&#64;\fR to insert a
551literal \fB@\fR without falling foul of the expansion syntax.
552.SS "Expansion Syntax"
553Expansions are surrounded by at ("@") symbols take the form of a keyword
554followed by zero or more arguments. Arguments may either be quoted by curly
555brackets ("{" and "}") or separated by colons (":"). Both kinds may be mixed
556in a single expansion, though doing so seems likely to cause confusion.
557The descriptions below contain suggested forms for each
558expansion.
559.PP
560Leading and trailing whitespace in unquoted arguments is ignored, as is
561whitespace (including newlines) following a close bracket ("}").
562.PP
563Arguments are recursively expanded before being interpreted, except for
564\fITEMPLATE\fR arguments. These are expanded (possibly more than once) to
565produce the final expansion.
566(More than once means the same argument being expanded more than once
567for different tracks or whatever, not the result of the first
568expansion itself being re-expanded.)
569.PP
570Strings constructed by expansions (i.e. not literally copied from the template
571text) are SGML-quoted: any character which does not stand for itself in #PCDATA
572or a quoted attribute value is replaced by the appropriate numeric character
573reference.
574.PP
575The exception to this is that such strings are \fInot\fR quoted when they are
576generated in the expansion of a parameter.
577.PP
578In the descriptions below, the current track means the one set by
579\fB@playing@\fR, \fB@recent@\fR or \fB@queue@\fR, not the one that is playing.
580If none of these expansions are in force then there is no current track.
581\fIBOOL\fR should always be either \fBtrue\fR or \fBfalse\fR.
582.SS "Expansions"
583The following expansion keywords are defined:
584.TP
585.B @#{\fICOMMENT\fB}@
586Ignored.
587.TP
588.B @action@
589The current action. This reports
590.B manage
591if the action is really
592.B playing
593but
594.B mgmt=true
595was set.
596.TP
597.B @and{\fIBOOL\fB}{\fIBOOL\fB}\fR...\fB@
598If there are no arguments, or all the arguments are \fBtrue\fB, then expands to
599\fBtrue\fR, otherwise to \fBfalse\fR.
600.TP
601.B @arg:\fINAME\fB@
602Expands to the value of CGI script argument \fINAME\fR.
603.TP
604.B @basename@
605The basename of the current directory component, in \fB@navigate@\fR.
606.TP
607.B @basename{\fIPATH\fB}@
608The base name part of \fIPATH\fR.
609.TP
610.B @choose{\fIWHAT\fB}{\fITEMPLATE\fB}@
611Expands \fITEMPLATE\fR repeatedly for each file or directory under
612\fB@arg:directory@\fR.
613\fIWHAT\fR should be either \fBfile\fR or \fBdirectory\fR.
614Use \fB@file@\fR to get the display name or filename of the file or
615directory.
616Usually used in \fBchoose.html\fR.
617.TP
618.B @dirname@
619The directory of the current directory component, in \fB@navigate@\fR.
620.TP
621.B @dirname{\fIPATH\fB}@
622The directory part of \fIPATH\fR.
623.TP
624.B @enabled@
625Expands to \fBtrue\fR if play is currently enabled, otherwise to \fBfalse\fR.
626.TP
627.B @eq{\fIA\fB}{\fIB\fB}
628Expands to \fBtrue\fR if \fIA\fR and \fIB\fR are identical, otherwise to
629\fBfalse\fR.
630.TP
631.B @file@
632Expands to the filename of the current file or directory, inside the template
633argument to \fBchoose\fR.
634.TP
635.B @files{\fITEMPLATE\fB}
636Expands \fITEMPLATE\fB once for each file indicated by the \fBdirectory\fR CGI
637arg if it is present, or otherwise for the list of files counted by \fBfiles\fR
638with names \fB0_file\fR, \fB1_file\fR etc.
639.TP
640.B @fullname@
641The full path of the current directory component, in \fB@navigate@\fR.
642.TP
643.B @id@
644The ID of the current track.
645.TP
646.B @if{\fIBOOL\fB}{\fITRUEPART\fB}{\fIFALSEPART\fB}@
647If \fIBOOL\fR expands to \fBtrue\fR then expands to \fITRUEPART\fR, otherwise
648to \fIFALSEPART\fR (which may be omitted).
649.TP
650.B @include:\fIPATH\fR@
651Include the named file as if it were a template file. If \fIPATH\fR
652starts with a \fB/\fR then it is used as-is; otherwise, ".html" is
653appended and the template path is searched.
654.TP
655.B @index@
656Expands to the index of the current file in \fB@queue@\fR, \fB@recent@\fR or
657\fB@files@\fR.
658.TP
659.B @isdirectories@
660Expands to \fBtrue\fR if there are any directories in \fB@arg:directory@\fR,
661otherwise to \fBfalse\fR.
662.TP
663.B @isfiles@
664Expands to \fBtrue\fR if there are any files in \fB@arg:directory@\fR,
665otherwise to \fBfalse\fR.
666.TP
667.B @isfirst@
668Expands to \fBtrue\fR if this is the first repetition of a \fITEMPLATE\fR
669argument in a loop (\fB@queue\fR or similar), otherwise to \fBfalse\fR.
670.TP
671.B @islast@
672Expands to \fBtrue\fR if this is the last repetition of a \fITEMPLATE\fR in a
673loop, otherwise to \fBfalse\fR.
674.TP
675.B @isplaying@
676Expands to \fBtrue\fR if a track is playing, otherwise to \fBfalse\fR.
677.TP
678.B @isqueue@
679Expands to \fBtrue\fR if there are any tracks in the queue, otherwise to
680\fBfalse\fR.
681.TP
682.B @isrecent@
683Expands to \fBtrue\fR if the recently played list has any tracks in it,
684otherwise to \fBfalse\fR.
685.TP
686.B @label:\fINAME\fR\fB@
687Expands to the value of label \fINAME\fR. See the shipped \fIoptions.labels\fR
688file for full documentation of the labels used by the standard templates.
689.TP
690.B @length@
691Expands to the length of the current track.
692.TP
693.B @navigate{\fIDIRECTORY\fB}{\fITEMPLATE\fB}
694Expands \fITEMPLATE\fR for each component of \fIDIRECTORY\fR in turn.
695Use \fB@dirname\fR and \fB@basename@\fR to get the components of the path to
696each component.
697Usually used in \fBchoose.html\fR.
698.TP
699.B @ne{\fIA\fB}{\fIB\fB}
700Expands to \fBtrue\fR if \fIA\fR and \fIB\fR differ, otherwise to \fBfalse\fR.
701.TP
702.B @nfiles@
703Expands to the number of files from \fB@files\fR (above).
704.TP
705.B @nonce@
706Expands to a string including the time and process ID, intended to be
707unique across invocations.
708.TP
709.B @not{\fIBOOL\fB}@
710Expands to \fBfalse\fR if \fIBOOL\fR is \fBtrue\fR, otherwise to
711\fBfalse\fR.
712.TP
713.B @or{\fIBOOL\fB}{\fIBOOL\fB}\fR...\fB@
714If at least one argument is \fBtrue\fB, then expands to \fBtrue\fR, otherwise
715to \fBfalse\fR.
716.TP
717.B @parity@
718Expands to \fBeven\fR or \fBodd\fR depending on whether the current track is at
719an even or odd position in \fB@queue@\fR, \fB@recent@\fR or \fB@files@\fR.
720.TP
721.B @part{\fICONTEXT\fB}{\fIPART\fB}@
722Expands to track name part \fIPART\fR using context \fICONTEXT\fR for the
723current track. The context may be omitted (and normally would be) and defaults
724to \fBdisplay\fR.
725.TP
726.B @part{\fICONTEXT\fB}{\fIPART\fB}{\fITRACK\fB}@
727Expands to track name part \fIPART\fR using context \fICONTEXT\fR for
728\fITRACK\fR. In this usage the context may not be omitted.
729.TP
730.B @paused@
731Expands to \fBtrue\fR if the current track is paused, else \fBfalse\fR.
732.TP
733.B @playing{\fITEMPLATE\fB}@
734Expands \fITEMPLATE\fR using the playing track as the current track.
735.TP
736.B @pref{\fITRACK\fB}{\fIKEY\fB}@
737Expand to the track preference, or the empty string if it is not set.
738.TP
739.B @prefname@
740Expands to the name of the current preference, in the template
741argument of \fB@prefs@\fR.
742.TP
743.B @prefs{\fIFILE\fB}{\fITEMPLATE\fB}@
744Expands \fITEMPLATE\fR repeatedly, for each preference of track
745\fIFILE\fR.
746Use \fB@prefname@\fR and \fB@prefvalue@\fR to get the name and value.
747.TP
748.B @prefvalue@
749Expands to the value of the current preference, in the template
750argument of \fB@prefs@\fR.
751.TP
752.B @queue{\fITEMPLATE\fB}@
753Expands \fITEMPLATE\fR repeatedly using the each track on the queue in turn as
754the current track. The track at the head of the queue comes first.
755.TP
756.B @random-enabled@
757Expands to \fBtrue\fR if random play is currently enabled, otherwise to
758\fBfalse\fR.
759.TP
760.B @recent{\fITEMPLATE\fB}@
761Expands \fITEMPLATE\fR repeatedly using the each recently played track in turn
762as the current track. The most recently played track comes first.
763.TP
764.B @resolve{\fITRACK\fB}@
765Resolve aliases for \fITRACK\fR and expands to the result.
766.TP
767.B @search{\fIPART\fB}\fR[\fB{\fICONTEXT\fB}\fR]\fB{\fITEMPLATE\fB}@
768Expands \fITEMPLATE\fR once for each group of search results that have
769a common value of track part \fIPART\fR.
770The groups are sorted by the value of the part.
771.IP
772.B @part@
773and
774.B @file@
775within the template will apply to one of the tracks in the group.
776.IP
777If \fICONTEXT\fR is specified it should be either \fBsort\fR or \fBdisplay\fR,
778and determines the context for \fIPART\fR. The default is \fBsort\fR. Usually
779you want \fBdisplay\fR for everything except the title and \fBsort\fR for the
780title. If you use \fBsort\fR for artist and album then you are likely to get
781strange effects.
782.TP
783.B @server-version@
784Expands to the server's version string.
785.TP
786.B @shell{\fICOMMAND\fB}@
787Expands to the output of \fICOMMAND\fR executed via the shell. \fBsh\fR is
788searched for using \fBPATH\fR. If the command fails then this is logged but
789otherwise ignored.
790.TP
791.B @state@
792In \fB@queue@\fR and \fB@recent@\fR, expands to the state of the current
793track. Otherwise the empty string. Known states are:
794.RS
795.TP 12
796.B failed
797The player terminated with nonzero status, but not because the track was
798scratched.
799.TP
800.B isscratch
801A scratch, in the queue.
802.TP
803.B no_player
804No player could be found.
805.TP
806.B ok
807Played successfully.
808.TP
809.B random
810A randomly chosen track, in the queue.
811.TP
812.B scratched
813This track was scratched.
814.TP
815.B unplayed
816An explicitly queued track, in the queue.
817.RE
818.IP
819Some additional states only apply to playing tracks, so will never be seen in
820the queue or recently-played list:
821.RS
822.TP 12
823.B paused
824The track has been paused.
825.TP
826.B quitting
827Interrupted because the server is shutting down.
828.TP
829.B started
830This track is currently playing.
831.RE
832.TP
833.B @stats@
834Expands to the server statistics.
835.TP
836.B @thisurl@
837Expands to the URL of the current page. Typically used in
838.B back
839arguments. If there is a
840.B nonce
841argument then it is changed to a fresh value.
842.TP
843.B @track@
844The current track.
845.TP
846.B @trackstate{\fIPATH\fB}@
847Expands to the current track state: \fBplaying\fR if the track is actually
848playing now, \fBqueued\fR if it is queued or the empty string otherwise.
849.TP
850.B @transform{\fIPATH\fB}{\fITYPE\fB}{\fICONTEXT\fB}@
851Transform a path according to \fBtransform\fR (see above).
852\fIPATH\fR should be a raw filename (of a track or directory).
853\fITYPE\fR should be the transform type (e.g. \fItrack\fR or \fIdir\fR).
854\fICONTEXT\fR should be the context, and can be omitted (the default
855is \fBdisplay\fR).
856.TP
857.B @url@
858Expands to the canonical URL as defined in \fIpkgconfdir/config\fR.
859.TP
860.B @urlquote{\fISTRING\fB}@
861URL-quote \fISTRING\fR.
862.TP
863.B @version@
864Expands to \fBdisorder.cgi\fR's version string.
865.TP
866.B @volume:\fISPEAKER\fB@
867The volume on the left or right speaker. \fISPEAKER\fR must be \fBleft\fB or
868\fBright\fR.
869.TP
870.B @when@
871When the current track was played (or when it is expected to be played, if it
872has not been played yet)
873.TP
874.B @who@
875Who submitted the current track.
876.SH "WEB OPTIONS"
877This is a file called \fIoptions\fR, searched for in the same manner
878as templates. It includes numerous options for the control of the web
879interface. The general syntax is the same as the main configuration
880file, except that it should be encoded using UTF-8 (though this might
881change to the current locale's character encoding; stick to ASCII to
882be safe).
883.PP
884The shipped \fIoptions\fR file includes four standard options files.
885In order, they are:
886.TP
887.I options.labels
888The default labels file. You wouldn't normally edit this directly - instead
889supply your own commands in \fIoptions.user\fR. Have a look at the shipped
890version of the file for documentation of labels used by the standard templates.
891.TP
892.I options.user
893A user options file. Here you should put any overrides for the default
894labels and any extra labels required by your modified templates.
895.PP
896Valid directives are:
897.TP
898.B columns \fINAME\fR \fIHEADING\fR...
899Defines the columns used in \fB@playing@\fR and \fB@recent@\fB. \fINAME\fR
900must be either \fBplaying\fR, \fBrecent\fR or \fBsearch\fR.
901\fIHEADING\fR... is a list of
902heading names. If a column is defined more than once then the last definitions
903is used.
904.IP
905The heading names \fBbutton\fR, \fBlength\fR, \fBwhen\fR and \fBwho\fR
906are built in.
907.TP
908.B include \fIPATH\fR
909Includes another file. If \fIPATH\fR starts with a \fB/\fR then it is
910taken as is, otherwise it is searched for in the template path.
911.TP
912.B label \fINAME\fR \fIVALUE\fR
913Define a label. If a label is defined more than once then the last definition
914is used.
915.SS Labels
916Some labels are defined inside \fBdisorder.cgi\fR and others by the
917default templates. You can define your own labels and use them inside
918a template.
919.PP
920When an undefined label is expanded, if it has a dot in its name then
921the part after the final dot is used as its value. Otherwise the
922whole name is used as the value.
923.PP
924Labels are no longer documented here, see the shipped \fIoptions.labels\fR file
925instead.
926.SH "REGEXP SUBSTITUTION RULES"
927Regexps are PCRE regexps, as defined in \fBpcrepattern\fR(3). The
928only option used is \fBPCRE_UTF8\fR. Remember that the configuration
929file syntax means you have to escape backslashes and quotes inside
930quoted strings.
931.PP
932In a \fISUBST\fR string the following sequences are interpreted
933specially:
934.TP
935.B $1 \fR... \fB$9
936These expand to the first to ninth bracketed subexpression.
937.TP
938.B $&
939This expands to the matched part of the subject string.
940.TP
941.B $$
942This expands to a single \fB$\fR symbol.
943.PP
944All other pairs starting with \fB$\fR are undefined (and might be used
945for something else in the future, so don't rely on the current
946behaviour.)
947.PP
948If \fBi\fR is present in \fIREFLAGS\fR then the match is case-independent. If
949\fBg\fR is present then all matches are replaced, otherwise only the first
950match is replaced.
951.SH "ACTIONS"
952What the web interface actually does is terminated by the \fBaction\fR CGI
953argument. The values listed below are supported.
954.PP
955Except as specified, all actions redirect back to the \fBplaying.html\fR
956template unless the \fBback\fR argument is present, in which case the URL it
957gives is used instead.
958.PP
959Redirection to \fBplaying.html\fR preserves \fBmgmt=true\fR if it is present.
960.TP 8
961.B "move"
962Move track \fBid\fR by offset \fBdelta\fR.
963.TP
964.B "play"
965Play track \fBfile\fR, or if that is missing then play all the tracks in
966\fBdirectory\fR.
967.TP
968.B "playing"
969Don't change any state, but instead compute a suitable refresh time and include
970that in an HTTP header. Expands the \fBplaying.html\fR template rather than
971redirecting.
972.IP
973This is the default if \fBaction\fR is missing.
974.TP
975.B "random-disable"
976Disables random play.
977.TP
978.B "random-enable"
979Enables random play.
980.TP
981.B "disable"
982Disables play completely.
983.TP
984.B "enable"
985Enables play.
986.TP
987.B "pause"
988Pauses the current track.
989.TP
990.B "remove"
991Remove track \fBid\fR.
992.TP
993.B "resume"
994Resumes play after a pause.
995.TP
996.B "scratch"
997Scratch the playing track. If \fBid\fR is present it must match the playing
998track.
999.TP
1000.B "volume"
1001Change the volume by \fBdelta\fR, or if that is missing then set it to the
1002values of \fBleft\fR and \fBright\fR. Expands to the \fBvolume.html\fR template
1003rather than redirecting.
1004.TP
1005.B "prefs"
1006Adjust preferences from the \fBprefs.html\fR template (which it then expands
1007rather than redirecting).
1008.IP
1009If
1010.B parts
1011is set then the cooked interface is assumed. The value of
1012.B parts
1013is used to determine which trackname preferences are set. By default the
1014.B display
1015context is adjusted but this can be overridden with the
1016.B context
1017argument. Also the
1018.B random
1019argument is checked; if it is set then random play is enabled for that track,
1020otherwise it is disabled.
1021.IP
1022Otherwise if the
1023.B name
1024and
1025.B value
1026arguments are set then they are used to set a single preference.
1027.IP
1028Otherwise if just the
1029.B name
1030argument is set then that preference is deleted.
1031.IP
1032It is recommended that links to the \fBprefs\fR action use \fB@resolve@\fR to
1033enure that the real track name is always used. Otherwise if the preferences
1034page is used to adjust a trackname_ preference, the alias may change, leading
1035to the URL going stale.
1036.TP
1037.B "error"
1038This action is generated automatically when an error occurs connecting to the
1039server. The \fBerror\fR label is set to an indication of what the error is.
1040.SH "TRACK NAME PARTS"
1041The traditional track name parts are \fBartist\fR, \fBalbum\fR and \fBtitle\fR,
1042with the obvious intended meaning. These are controlled by configuration and
1043by \fBtrackname_\fR preferences.
1044.PP
1045In addition there are two built-in parts, \fBpath\fR which is the whole path
1046name and \fBext\fR which is the filename extension, including the initial dot
1047(or the empty string if there is not extension).
1048.SH "SEE ALSO"
77cfc7a2 1049\fBdisorder\fR(1), \fBsox\fR(1), \fBdisorderd\fR(8), \fBdisorder-dump\fR(8),
460b9539 1050\fBpcrepattern\fR(3)
1051.\" Local Variables:
1052.\" mode:nroff
1053.\" fill-column:79
1054.\" End: