technology, scones, nonsense







Subscribe to my RSS Feed



This section describes the basic concepts involved in configuring sconeserver.


Sconeserver is configured using a simple but powerful object-orientated language called sconescript. Sconescript commands can either be read from a file, or run interactively from a configuration console. This is roughly analogous to running a shell script or batch file versus entering commands in an interactive shell.

Sconescript uses a syntax which is similar to JavaScript. Commands always execute within the context of an object, which in the case of a configuration file, will be the module being configured. Every object can have any number of properties, methods and sub-objects, which should be well described in the module's documentation.

Main configuration file - sconeserver.conf

On startup, the root module sconeserver reads its configuration from the file /etc/sconeserver/sconeserver.conf, unless an alternative path has been specified on the command line. The sconeserver root module page has more information on the configuration options available here.


By default sconeserver will load all modules that have a conf file that is present in /etc/sconeserver/modules.d. Each module conf file may specify dependent modules, which must be present and loaded before the particular module can be loaded. The conf file can also be used to set any global options the module may have - see the module documentation for details.

Site configuration

Configuration that is specific to the site should go under /etc/sconeserver/sites.d, with each logical site or service having its own .conf file (files with any other extension will be ignored).

Command line options

-v, --version

Print version information and exit.

-h, --help

Print help on command line options and exit.


Start in foreground mode. In this mode, sconed does not become a daemon process, and a configuration console is connected to the terminal to allow commands to be issued. Issuing the "exit" command from this console will shutdown Sconeserver.


Don't read any configuration on startup. Starts a completely unconfigured Sconeserver. Probably not a lot of use without also specifying "-f". This mode is used by the automatic tests.


Use an alternative path to configuration files, instead of the default "prefix/etc".


Use an alternative module path, instead of the default $PREFIX/lib/sconeserver.


Use an alternative path for variable or log files, instead of the default "prefix/var".


Specifies a file to which the daemon's process ID is written.

Updated on 2013-11-06 08:58:01 +0000 | Requested on 2022-12-02 16:52:41 +0000