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