From afbd9895bfae15e2f33b3bc1ffd6b5ea6ea3f542 Mon Sep 17 00:00:00 2001 From: Stein Magnus Jodal Date: Sat, 29 Mar 2014 21:14:35 +0100 Subject: [PATCH] docs: Make 'mopidy config' more prominent --- docs/config.rst | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/docs/config.rst b/docs/config.rst index 740b1f1e..3e228344 100644 --- a/docs/config.rst +++ b/docs/config.rst @@ -26,13 +26,18 @@ will create an empty config file for you and print what config values must be set to successfully start Mopidy. When you have created the configuration file, open it in a text editor, and add -the config values you want to change. If you want to keep the default for a -config value, you **should not** add it to -:file:`~/.config/mopidy/mopidy.conf`. +the config values you want to change. If you want to keep the default for a +config value, you **should not** add it to the config file, but leave it out so +that when we change the default value in a future version, you won't have to +change your configuration accordingly. To see what's the effective configuration for your Mopidy installation, you can -run ``mopidy config``. It will print your full effective config with passwords -masked out so that you safely can share the output with others for debugging. +run:: + + mopidy config + +This will print your full effective config with passwords masked out so that +you safely can share the output with others for debugging. You can find a description of all config values belonging to Mopidy's core below, together with their default values. In addition, all :ref:`extensions