| 1 |
.. _daemon_configuration: |
| 2 |
|
| 3 |
Configuration |
| 4 |
============= |
| 5 |
|
| 6 |
WirePlumber is a heavily modular daemon. By itself, it doesn't do anything |
| 7 |
except load its configured components. The actual management logic is |
| 8 |
implemented inside those components. |
| 9 |
|
| 10 |
At startup, WirePlumber reads its configuration file (combined with all the |
| 11 |
fragments it may have) and loads the components specified in the selected |
| 12 |
profile. This configures the operation context. Then, the components take over |
| 13 |
and drive the entirety of the daemon's operation. |
| 14 |
|
| 15 |
The sections below describe in more detail the configuration file format and |
| 16 |
the various options available. |
| 17 |
|
| 18 |
.. toctree:: |
| 19 |
:maxdepth: 1 |
| 20 |
|
| 21 |
configuration/conf_file.rst |
| 22 |
configuration/components_and_profiles.rst |
| 23 |
configuration/configuration_option_types.rst |
| 24 |
configuration/modifying_configuration.rst |
| 25 |
configuration/migration.rst |
| 26 |
configuration/features.rst |
| 27 |
configuration/settings.rst |
| 28 |
configuration/alsa.rst |
| 29 |
configuration/bluetooth.rst |
| 30 |
configuration/access.rst |