@@ -3,12 +3,7 @@ Configuration
33=============
44
55Both the :doc: `CLI <cli >` and the :doc: `web application <app >` can
6- be configured from a file.
7-
8- .. warning ::
9-
10- The configuration file format is not stable yet
11- and might change without any notice.
6+ be configured from a TOML file.
127
138.. note ::
149
@@ -21,17 +16,15 @@ The configuration file path can be specified either through the ``--config``
2116CLI option or through the ``READER_CONFIG `` environment variable
2217(also usable with the web application).
2318
24- The config file is split in contexts;
25- this allows having a set of global defaults
26- and overriding them with CLI- or web-app-specific values.
27- Use the ``config dump --merge `` command
28- to see the final configuration for each context.
29-
30- The older ``READER_DB ``, ``READER_PLUGIN ``, and ``READER_APP_PLUGIN ``
31- environment variables always *replace * the corresponding config values,
32- so they should be used only for debugging.
19+ The configuration file matches the shape of the :doc: `CLI <cli >`
20+ (the ``reader `` section has options for the ``reader `` command,
21+ the ``reader.update `` section has options for the ``reader update `` command, etc.).
22+ In general, option names match those in the CLI
23+ (``--feed-root `` -> ``feed_root ``);
24+ options that can be passed multiple times in the CLI
25+ are pluralized in the config
26+ (``--cli-plugin `` -> ``cli_plugins ``).
3327
34- The following example shows the config file structure
35- and the options currently available:
28+ Example:
3629
3730.. literalinclude :: ../examples/config.toml
0 commit comments