9
Drizzle can draw its configuration from a number of sources, including the
10
command line, configuration files and environment variables.
12
Support is planned for pluggable configuration souces.
18
Drizzle first reads the command line options dealing with config file
19
location. These options may only be given as command line options.
20
Then, the config files are parsed, for all options. After that,
21
environment variables are processed, and any value given in them will
22
override values input from the config files. Finally, values on the command
23
line will be processed and any options given here take final precedence.
29
Command line options are of the form `--option-name=value`. There are some
30
boolean flags, such as `--help` which do not require (nor can accept) an
33
|more| See :ref:`options` for all options that :program:`drizzled`
36
Environment variables are the same as the command line options, except that
37
the variable name is prefixed with *DRIZZLED_*, in all caps and all `.` and
38
`-` are turned into underscores. So the option
39
`--innodb.buffer_pool_size=10` could be given in the environment variable
40
*DRIZZLED_INNODB_BUFFER_POOL_SIZE*
42
The config files contain a set of lines of the form `option-name=value`, one
43
per line. Due to a bug in Boost.Program_options Boolean values require an argument, e.g. `console.enable=true`.
45
Config files support section headers such as `[innodb]` with all options
46
occuring subsequently being prefixed by the section header. For instance, if
53
It would be the same as::
55
innodb.buffer_pool_size=10M
added
removed
docs/configuration.rst
