queue.conf | codebunny.org

Overview

queue.conf covers details relating to the receiving of input files and defines directories and available transport methods. Currently supported transports are:

cp - Straight file copy. Use for cases where the client and server are on the same machine, or the client can write to a directory on the server via NFS or similar
scp - Secure copy. Copy to a network location using the scp secure copy program. The user must be able to log-on to the server without using a password, e.g. by using the authorized_keys setting in ssh
ftp - Good ol' FTP. Available from Wagtail 0.4. The user must be able to log-on to the server without using a password, e.g. by using an appropriate .netrc entry

Wagtail versions 0.1-0.3 required each transport method to have its own section and set of data. This sucked. Version 0.4 allows a global set of data to be defined which applies to each transport method. You can, if you like, define sections for each method, the values in which will override the global settings. Pre-0.4 configuration files will still work in 0.4, since each section is effectively overriding defaults which aren't defined.

Sections

Global

Key	Example value	Description
default-dir	/media/audio/queue/	The directory to copy files to from the point of view of the client. Used by all transports.
default-host	wagserver	The hostname of the server machine. Used by scp and ftp transports.
source-dir	/media/audio/queue/	Specifies where the source files are placed from the point of view of the encoder.
pref-transport	cp	If specified this identifies which of the transports defined in the following sections is the preferred transport. A client should use this transport if possible.
source-dir	/media/audio/queue/	Specifies where the source files are placed from the point of view of the encoder.
transport-allow	cp,scp,ftp	Comma separated list of transports to advertise. If this key is absent the list of section headings is used instead, but note this is just a backwards compatible trick and as a rule you should specify transport-allow.

Other

Each `override' section is simply named after the transport it refers to. Keys within the section are the same as for the global section with 'default' omitted, e.g. host instead of default-host.